"But it's not going to be at the v8 level." A few years back one of the v8 > devs said (in a post on this list, but i have no link handy) that v8 does > not gc at shutdown because (i'm paraphrasing), "it negatively impacts > Chrome's shutdown time." i think most of us will agree that shutting down > cleanly is better than shutting down quickly, but JS was not really > intended (it was pointed out in that thread or a similar one) to be used > with types which require proper destructor calls to ensure proper behaviour > of the system. > > So, that's a "positive" answer in the sense that i'm positive v8 will > never guaranty such a feature. v8's only _real_ concern, as far as directly > adapting to customer needs, is Chromium and friends. (That's based off of > my own observations over my years on this list, and not a sentiment > expressed directly from anyone working on v8 (more implied by various > answers they've provided).) >
That's not positive at all! The past doesn't matter. Nor does something that somebody said x months ago. Please spare us from meaningless speculation. Software evolves and changes all the time. (threading support via Isolates are an example of this) Passing an optional boolean to indicate that full GC at shutdown is desired is very easy to add. -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
