Irakli Gozalishvili wrote:
I really need to know why WeakMaps don't accept primitives as keys,
can anyone please reply ?
How would the GC know when to remove the entry from the map? Because a
primitive is never (or always, if wrapped) eligible for
garbage-collection, a WeakMap does not help
Jorge wrote:
or some other creative way of statically encoding the might suspend
execution condition into the syntax?
Yes, of course, it would be fine. Why ?
Because this is the crux of the run-to-completion debate that we're
immersed in.
Right now, JS has run-to-completion, where
Brendan Eich wrote:
On Oct 21, 2011, at 12:49 PM, Eric Jacobs wrote:
The catch is, of course, that all code which either can yield, or can call other
functions which yield, must have the yield keyword there, to mark that
run-to-completion invariants will end at that point. This seems like
Kris Zyp wrote:
I believe that the overwhelming need that is continually and
constantly expressed and felt in the JS community in terms of handling
asynchronous activity is fundamentally a cry for top-down controlled
single-frame continuations (obviously not always stated in such terms,
4 matches
Mail list logo
