I want to apologize for the ambiguity here. You can find the current tentative draft API [in this issue comment](https://github.com/tc39/proposal-weakrefs/issues/55#issuecomment-444513178). This draft API does include a way to register a finalizer callback. We saw this as important, at the very least, because we don't want to encourage polling for a WeakRef to "go null". > As to integration with other web platform APIs, the various DOM collection types seem like they might benefit from WeakRefs, but it isn't yet clear to me if that will need to be done though new types or if compatible evolution of existing collections. Could you say something more about where you see WeakRefs tying into the web platform? My understanding was that the DOM collections which make GC visible were seen as a mistake not to be repeated. One reason why I thought TAG guidance would be useful here is that the design principles recommend against exposing GC, see https://github.com/w3ctag/design-principles/issues/100 . -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/321#issuecomment-461105998
Received on Wednesday, 6 February 2019 17:19:22 UTC