Re: [v8-users] Intent to ship: BigInt, BigInt64Array, BigUint64Array
LGTM for V8! On Fri, Mar 2, 2018 at 11:25 AM, Jakob Kummerow wrote: > Note that this is a v8/JavaScript feature, so this post is just an FYI for > blink-dev — no signoff from Blink API owners is required. > > > *Contact emails* > > jkumme...@chromium.org, n...@chromium.org > > > *Explainer* > > https://github.com/tc39/proposal-bigint/blob/master/README.md > > > *Spec* > > https://tc39.github.io/proposal-bigint > > > *Summary* > > This proposal brings arbitrary-precision integers to JavaScript, along > with new TypedArrays with signed and unsigned 64-bit integer elements. > > > *Is this feature supported on all six Blink platforms (Windows, Mac, > Linux, Chrome OS, Android, and Android WebView)?* > > Yes. > > > *Debuggability* > > As of this writing, DevTools support is being worked on. It will be > available before shipping. > > All the usual DevTools features will work for code containing BigInts. > > > *Interoperability risk* > > Edge: No public signals > > Firefox: In development: https://bugzilla.mozilla.org/ > show_bug.cgi?id=1366287 > > Safari: In development: https://bugs.webkit.org/show_bug.cgi?id=179001 > > Web developers: Positive, e.g. https://github.com/tc39/ > proposal-bigint/issues/53 > > > *Compatibility risk* > > BigInt literals were invalid syntax before. > > The "BigInt", "BigInt64Array", "BigUint64Array" constructors could clash > with user-defined globals. > > > *Activation risk* > > The semantics of the BigInt proposal are not polyfillable (it would > require operator overloading). > > > *Tests* > > test262 contains tests for BigInt, BigInt64Array, BigUintArray, which V8 > passes. > > V8 also has its own tests: https://chromium.googlesource. > com/v8/v8/+/master/test/mjsunit/harmony/bigint > > > *Tracking bug* > > crbug.com/v8/6791 > > > *Entry on the feature dashboard* > > https://www.chromestatus.com/features/5371603852460032 > > > *Requesting approval to ship?* > > Yes. > > We would like to ship BigInts on ToT in ~3 weeks, in time for Chrome 67. > > > -- > -- > v8-users mailing list > v8-users@googlegroups.com > 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 v8-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- -- v8-users mailing list v8-users@googlegroups.com 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 v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [v8-users] Re: [v8-dev] Intent to ship: BigInt, BigInt64Array, BigUint64Array
Thanks for emailing me! No, I haven’t been hacked :) I signed up for a spam filtering service called BitBounce. To deliver your email to my inbox, please click the link below. Thanks! https://bitbounce.com/pay_bitbounce_fee/2673215213 BitBounce is a product by: Turing Technology, Inc. BitBounce.com Redwood City, CA -- -- v8-users mailing list v8-users@googlegroups.com 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 v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [v8-users] Are functions which defined using eval or new Function() optimized?
Functions created with eval or new Function will get optimized (after a while, just like other functions -- nothing is optimized on first use). That said, modifying prototypes after the fact tends to have a performance impact, because V8 makes optimizations (all over the place) based on the assumption that prototypes don't change much. When they do, optimized code built on such assumptions must be discarded. That may or may not be an issue for your use case, the only way to find out is to try. On Fri, Mar 2, 2018 at 7:47 AM Koray wrote: > Forwarding here from Node.js group as this one is more appropriate. > > Hello, > > I have a real time application which will require constant updates / > bug fixes. So I will be constantly defining new functions on > prototypes or constructors. > > My question is, will there be a difference between functions which > were hard coded and functions defined using eval or Function > constructor? If so, will require() be possibly able to get around > this? > > Note: Functions will be used multiple times throughout the lifetime of > the application. Giving this information just in case if they are > being optimized after the first usage. > Thank you > > -- > -- > v8-users mailing list > v8-users@googlegroups.com > 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 v8-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- -- v8-users mailing list v8-users@googlegroups.com 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 v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[v8-users] Re: [v8-dev] Intent to ship: BigInt, BigInt64Array, BigUint64Array
🎉 On Fri, Mar 2, 2018 at 8:25 PM Jakob Kummerow wrote: > Note that this is a v8/JavaScript feature, so this post is just an FYI for > blink-dev — no signoff from Blink API owners is required. > > > *Contact emails* > > jkumme...@chromium.org, n...@chromium.org > > > *Explainer* > > https://github.com/tc39/proposal-bigint/blob/master/README.md > > > *Spec* > > https://tc39.github.io/proposal-bigint > > > *Summary* > > This proposal brings arbitrary-precision integers to JavaScript, along > with new TypedArrays with signed and unsigned 64-bit integer elements. > > > *Is this feature supported on all six Blink platforms (Windows, Mac, > Linux, Chrome OS, Android, and Android WebView)?* > > Yes. > > > *Debuggability* > > As of this writing, DevTools support is being worked on. It will be > available before shipping. > > All the usual DevTools features will work for code containing BigInts. > > > *Interoperability risk* > > Edge: No public signals > > Firefox: In development: > https://bugzilla.mozilla.org/show_bug.cgi?id=1366287 > > Safari: In development: https://bugs.webkit.org/show_bug.cgi?id=179001 > > Web developers: Positive, e.g. > https://github.com/tc39/proposal-bigint/issues/53 > > > *Compatibility risk* > > BigInt literals were invalid syntax before. > > The "BigInt", "BigInt64Array", "BigUint64Array" constructors could clash > with user-defined globals. > > > *Activation risk* > > The semantics of the BigInt proposal are not polyfillable (it would > require operator overloading). > > > *Tests* > > test262 contains tests for BigInt, BigInt64Array, BigUintArray, which V8 > passes. > > V8 also has its own tests: > https://chromium.googlesource.com/v8/v8/+/master/test/mjsunit/harmony/bigint > > > *Tracking bug* > > crbug.com/v8/6791 > > > *Entry on the feature dashboard* > > https://www.chromestatus.com/features/5371603852460032 > > > *Requesting approval to ship?* > > Yes. > > We would like to ship BigInts on ToT in ~3 weeks, in time for Chrome 67. > > > -- > -- > v8-dev mailing list > v8-...@googlegroups.com > 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 v8-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- -- v8-users mailing list v8-users@googlegroups.com 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 v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[v8-users] Intent to ship: BigInt, BigInt64Array, BigUint64Array
Note that this is a v8/JavaScript feature, so this post is just an FYI for blink-dev — no signoff from Blink API owners is required. *Contact emails* jkumme...@chromium.org, n...@chromium.org *Explainer* https://github.com/tc39/proposal-bigint/blob/master/README.md *Spec* https://tc39.github.io/proposal-bigint *Summary* This proposal brings arbitrary-precision integers to JavaScript, along with new TypedArrays with signed and unsigned 64-bit integer elements. *Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?* Yes. *Debuggability* As of this writing, DevTools support is being worked on. It will be available before shipping. All the usual DevTools features will work for code containing BigInts. *Interoperability risk* Edge: No public signals Firefox: In development: https://bugzilla.mozilla.org/show_bug.cgi?id=1366287 Safari: In development: https://bugs.webkit.org/show_bug.cgi?id=179001 Web developers: Positive, e.g. https://github.com/tc39/proposal-bigint/issues/53 *Compatibility risk* BigInt literals were invalid syntax before. The "BigInt", "BigInt64Array", "BigUint64Array" constructors could clash with user-defined globals. *Activation risk* The semantics of the BigInt proposal are not polyfillable (it would require operator overloading). *Tests* test262 contains tests for BigInt, BigInt64Array, BigUintArray, which V8 passes. V8 also has its own tests: https://chromium.googlesource.com/v8/v8/+/master/test/mjsunit/harmony/bigint *Tracking bug* crbug.com/v8/6791 *Entry on the feature dashboard* https://www.chromestatus.com/features/5371603852460032 *Requesting approval to ship?* Yes. We would like to ship BigInts on ToT in ~3 weeks, in time for Chrome 67. -- -- v8-users mailing list v8-users@googlegroups.com 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 v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[v8-users] Performance impact of increasing Error.stackTraceLimit?
Hi, I am wondering what the performance impact would be if I would change *Error.stackTraceLimit* [1] to a high value (e.g. 1000?). The default of just 10 stack frames is little when the error bubbles through a long chain of promises for example. This change would be in production code, not just for testing, so I am a little bit nervous of the consequences this would have. Maybe someone can share some experiences with changing this value. Ben [1] https://github.com/v8/v8/wiki/Stack-Trace-API -- -- v8-users mailing list v8-users@googlegroups.com 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 v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[v8-users] Are functions which defined using eval or new Function() optimized?
Forwarding here from Node.js group as this one is more appropriate. Hello, I have a real time application which will require constant updates / bug fixes. So I will be constantly defining new functions on prototypes or constructors. My question is, will there be a difference between functions which were hard coded and functions defined using eval or Function constructor? If so, will require() be possibly able to get around this? Note: Functions will be used multiple times throughout the lifetime of the application. Giving this information just in case if they are being optimized after the first usage. Thank you -- -- v8-users mailing list v8-users@googlegroups.com 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 v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
