j On Sat, Nov 2, 2013 at 8:10 AM, <[email protected]> wrote: > Today's Topic Summary > > Group: http://groups.google.com/group/v8-dev/topics > > Issue 2937 in v8: Is there any plan to support es6? [2 Updates] > Issue 2979 in v8: Inconsistent way of checking Handle types [1 Update] > HeapProfiler: provide human readable names for code objects. (issue > 52643002) [1 Update] > > Issue 2937 in v8: Is there any plan to support es6? > > [email protected] Nov 01 08:01PM > > Comment #1 on issue 2937 by [email protected]: Is there any plan to support > es6? > http://code.google.com/p/v8/issues/detail?id=2937 > > Yes. > > Blog post. > http://blog.chromium.org/2012/02/future-of-javascript-take-peek-today.html > > Issues. > https://code.google.com/p/v8/issues/list?can=1&q=label%3AHarmony > > > > > -- > You received this message because this project is configured to send all > issue notifications to this address. > You may adjust your notification preferences at: > https://code.google.com/hosting/settings > > > > [email protected] Nov 02 12:02PM > > Updates: > Status: Invalid > > Comment #2 on issue 2937 by [email protected]: Is there any plan to > support es6? > http://code.google.com/p/v8/issues/detail?id=2937 > > (No comment was entered for this change.) > > -- > You received this message because this project is configured to send all > issue notifications to this address. > You may adjust your notification preferences at: > https://code.google.com/hosting/settings > > > > Issue 2979 in v8: Inconsistent way of checking Handle types > > [email protected] Nov 01 08:10PM > > Status: New > Owner: ---- > > New issue 2979 by [email protected]: Inconsistent way of checking Handle > types > http://code.google.com/p/v8/issues/detail?id=2979 > > include/v8.h uses a TYPE_CHECK macro: > use: > https://code.google.com/p/v8/source/browse/branches/bleeding_edge/include/v8.h#234 > definition: > https://code.google.com/p/v8/source/browse/branches/bleeding_edge/include/v8.h#179 > > src/handles.h use a slightly different implementation that is only enabled > in DEBUG: > https://code.google.com/p/v8/source/browse/branches/bleeding_edge/src/handles.h#56 > > > Is there a reason for the two different ways of checking? > > If not, I can put together a check for switching src/handles.h to > TYPE_CHECK. > > -- > You received this message because this project is configured to send all > issue notifications to this address. > You may adjust your notification preferences at: > https://code.google.com/hosting/settings > > > > HeapProfiler: provide human readable names for code objects. (issue > 52643002) > > [email protected] Nov 01 02:55PM > > https://codereview.chromium.org/52643002/diff/190001/src/heap-snapshot-generator.cc > File src/heap-snapshot-generator.cc (right): > > https://codereview.chromium.org/52643002/diff/190001/src/heap-snapshot-generator.cc#newcode1777 > src/heap-snapshot-generator.cc:1777: if > (reference_tags_[tags_index].index == all_index) { > On 2013/10/31 14:24:02, Yury Semikhatsky wrote: >> As discussed offline this should be >> while (reference_tags_[tags_index].index == all_index) ++tags_index; >> to work correctly in case there are empty groups. This can be > addressed >> separately though with a separate test. > > On the second look the current implementation is correct as the tags for > empty groups will be skipped in RootsReferencesExtractor::Synchronize > > https://codereview.chromium.org/52643002/ > > > > -- > -- > v8-dev mailing list > [email protected] > http://groups.google.com/group/v8-dev > --- > You received this message because you are subscribed to the Google Groups > "v8-dev" 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.
-- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" 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.
