Sam puts his finger on what weak references do that is unique. I don’t fully understand the point...https://twitter.com/samth/status/1151982821914873861 …
The totemic value of this argument is interesting to me as a cultural boundary, no matter how much lower this burden is in practice now that we're in a fully OSS-engine world.
-
-
I can't tell what you're trying to say here. Annex B.3.3 was written in a practically OSS-engine world. What has to be reverse-engineered in such a case is not the workings of any one implementation but the implicit standard.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
The notion of reachability depends on so many things, like collector timing, JIT optimizations, closure conversion rules. Is anybody who wants to make cross-compatible weak refs going to have to understand eg the circumstances under which Oilpan uses conservative stack scanning?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Given the depth of behavior that weak refs make observable, that is equivalent to saying there is no problem because we can all switch (piecemeal, perhaps) to the dominant engine. Also, it says that it's OK in practice for Chrome 96 to be restricted to the behavior of Chrome 69.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.