Re: [v8-users] How to build a fixed version of V8 and its dependencies.

This is not a direct answer to your question, but we already host prebuilt `d8` binaries for Linux on 32-bit and 64-bit architectures. We plan on doing the same for other operating systems: https://bugs.chromium.org/p/v8/issues/detail?id=5918 By using a precompiled binary, you could bypass

Re: [v8-users] Bug in v8/src/parsing/scanner?

On Fri, Dec 15, 2017 at 4:44 PM, J Decker wrote: > The code below comes from ScanString() > I noticed that if the scanner encounters a '\' before a c0 > kMaxAscii > HandleLeadSurrogate() (0xd800+0xdc00 surrogate handling) is no longer done. > > I tried to make a test file that

Re: [v8-users] Re: [blink-dev] Intent to Ship: RegExp named captures

For future reference: this landed in V8 v6.4.49 and should thus be available in Chrome 64. On Wed, Oct 18, 2017 at 7:09 PM, 'Sathya Gunasekaran' via blink-dev < blink-...@chromium.org> wrote: > LGTM2 > > On

[v8-users] Re: [blink-dev] Re: Intent to ship: Unicode property escapes in regular expressions

For future reference: this landed in V8 v6.4.276 and should thus be available in Chrome 64. On Thu, Nov 9, 2017 at 10:48 PM, Adam Klein wrote: > LGTM (for v8 signoff purposes). >

[v8-users] Re: Intent to ship: Unicode property escapes in regular expressions

Note that since this is a V8/JS feature, this post is just an FYI to blink-dev — no signoff from Blink API owners is required. On Thu, Nov 9, 2017 at 10:29 PM, Mathias Bynens wrote: > Contact emails > > yang...@chromium.org, math...@chromium.org > > Spec > >

Re: [v8-users] Re: [blink-dev] Intent to ship: Array.prototype.{flat,flatMap}

For future reference: this landed in V8 v6.9.* and should thus be available in Chrome 69. On Tue, May 29, 2018 at 4:22 PM Sathya Gunasekaran wrote: > LGTM > On Wed, May 23, 2018 at 11:26 AM Mathias

Re: [v8-users] Intent to Ship: Array.prototype.values

Third time’s the charm! 爛 On Wed, Jan 31, 2018 at 4:07 PM, Sathya Gunasekaran wrote: > Contact Emails: > gsat...@chromium.org > > Spec: > https://tc39.github.io/ecma262/#sec-array.prototype.values > > Summary: > The values() method returns a new Array Iterator object that

Re: [v8-users] --print-code does not work

Tracking issue for the removal of --print-code: https://bugs.chromium.org/p/v8/issues/detail?id=7437 On Fri, Feb 9, 2018 at 11:22 PM, Jakob Kummerow wrote: > If --print-opt-code prints nothing, then probably your function isn't > getting optimized. Try calling it more

Re: [v8-users] Re: [blink-dev] Intent to ship: JSON ⊂ ECMAScript

For future reference: this landed in V8 v6.6.257 and should thus be available in Chrome 66. On Fri, Feb 16, 2018 at 7:58 PM, Benedikt Meurer wrote: > LGTM! > > > On Fri, Feb

[v8-users] Re: [blink-dev] Intent to ship: JSON ⊂ ECMAScript

Note that since this is a V8/JS feature, this post is just an FYI to blink-dev — no signoff from Blink API owners is required. For ECMAScript features like this one, if a browser vendor would be opposed to this proposal, they would block its advancement at TC39. Given that this proposal already

Re: [blink-dev] Re: [v8-users] Intent to ship: String.prototype.trimStart / String.prototype.trimEnd

For future reference: this landed in V8 v6.6.253 and should thus be available in Chrome 66. On Fri, Feb 9, 2018 at 11:44 PM, Adam Klein wrote: > LGTM3! > > On Fri, Feb 9, 2018 at

Re: [v8-users] base64 encode/decode in v8

`btoa` (and `atob`) are indeed browser-specific APIs; they’re not part of ECMAScript and not implemented in V8. You could use a JavaScript implementation. https://github.com/mathiasbynens/base64 matches the browser APIs `btoa` and `atob` as closely as possible. On Mon, Aug 20, 2018 at 8:26 PM

[v8-users] Intent to Ship: globalThis

Contact emails math...@chromium.org Spec https://tc39.github.io/proposal-global/ Summary A Stage 3 proposal introduces globalThis, enabling a universal mechanism to access the global object even in strict functions or modules, regardless of the platform. Motivation It is difficult to write

Re: [v8-users] Is it possible to access the AST of the v8 engine, for a given JavaScript code?

Grab a debug build (not a release build!) and run d8 --print-ast foo.js. On Thu, Jul 5, 2018 at 2:39 PM czczcheng wrote: > I want to analysis the javascript code and modify it in some cases. > > -- > -- > v8-users mailing list > v8-users@googlegroups.com >

[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 > > >

[v8-users] Re: [blink-dev] Intent to Ship: Public class fields

LGTM On Wed, Oct 17, 2018 at 9:47 AM Sathya Gunasekaran wrote: > Contact Emails: > gsat...@chromium.org > > Spec: > https://github.com/tc39/proposal-class-fields > https://tc39.github.io/proposal-static-class-features/ > > The linked proposal includes private fields, but this intent to ship >

[v8-users] Re: [v8-dev] Re: Intent to Ship: Public class fields

With the upcoming (but separate) private fields proposal, the example evolves from: class IncreasingCounter { _count = 0; get value() { return this._count; } increment() { this._count++; } } ...into: class IncreasingCounter { #count = 0; get value() { return

[v8-users] Re: [v8-dev] Re: Intent to ship: Intl.ListFormat

LGTM2 On Thu, Nov 8, 2018 at 2:44 AM Sathya Gunasekaran wrote: > LGTM > > On Thu, Nov 8, 2018 at 12:20 AM Frank Tang wrote: > >> Spec >> >> https://tc39.github.io/proposal-intl-list-format >> >> Summary >> >> A Stage 3 proposal that introduces a new formatter under Intl. >> >> Intl.ListFormat

[v8-users] Intent to ship: well-formed JSON.stringify

Contact emails math...@chromium.org Spec https://github.com/tc39/proposal-well-formed-stringify Summary A Stage 3 proposal changes JSON.stringify to prevent it from returning ill-formed Unicode strings. Motivation RFC 8259 section 8.1

Re: [v8-users] Fwd: Intent to ship: Optimize await and AsyncFromSyncIterator

LGTM On Fri, Sep 28, 2018 at 9:26 AM Maya Lekova wrote: > > > > > > > > > > > *Contact emailsmslek...@chromium.org > Explainerhttps://docs.google.com/document/d/1kL08cz4lR6gO5b2FATNK3QAfS8t-6K6kdk88U-n8tug/edit?usp=sharing >

Re: [v8-dev] Re: [v8-users] Re: Intent to ship: Intl.RelativeTimeFormat

LGTM3 On Tue, Sep 25, 2018 at 10:46 AM Adam Klein wrote: > LGTM2 > > On Tue, Sep 25, 2018 at 2:35 AM Sathya Gunasekaran > wrote: > >> LGTM >> >> On Mon, Sep 24, 2018 at 5:35 PM Frank Tang wrote: >> >>> Spec >>> >>> https://tc39.github.io/proposal-intl-relative-time/ >>> >>> Summary >>> >>> A

[v8-users] Re: [blink-dev] Re: [v8-dev] Intent to Ship: RegExp @@matchAll / String.prototype.matchAll

LGTM∞ On Fri, Dec 14, 2018 at 7:37 AM Jakob Gruber wrote: > LGTM3 > > On Fri, Dec 14, 2018 at 1:57 AM Adam Klein wrote: > >> LGTM2 >> >> On Thu, Dec 13, 2018 at 3:27 PM Sathya Gunasekaran >> wrote: >> >>> LGTM >>> On Thu, Dec 13, 2018 at 2:01 PM Peter Wong >>> wrote: >>> > >>> > Contact

Re: [v8-users] runing v8

https://v8.dev/docs/embed is a good place to get started. On Thu, Dec 6, 2018 at 11:01 PM Idris AIT MOULAY wrote: > hi every body there some one here that can help to understand v8 code > source, and try to run it, there is any doc or reference that may help me > to understand v8 code source. >

Re: [blink-dev] Re: [v8-users] Intent to Ship: Numeric separators

LGTM now that the conflict has been resolved! On Thu, Mar 28, 2019 at 12:01 PM 'Sathya Gunasekaran' via blink-dev < blink-...@chromium.org> wrote: > On Thu, Mar 15, 2018 at 2:25 PM Adam Klein wrote: > > > > There's a possible conflict between this feature and another proposal, > Extended

Re: [v8-users] How to use Chrome Dev Tools to debug a script in d8

Does the documentation help? https://v8.dev/docs/inspector On Mon, Apr 8, 2019 at 1:23 PM DaManuell wrote: > I successfully built d8.exe from sources > > I made a simple JavaScrit file called test.js: > > function test( obj ) { > return obj.prop + obj.prop; > } > > I ran d8.exe with the

Re: [v8-users] Re: [blink-dev] Re: [v8-dev] Intent to ship: Private class fields

The v8-users mailing list is not the best place to discuss the design of new ECMAScript language features. This proposal reached Stage 3 of the TC39 process a long time ago, and each design decision has since been revisited and reaffirmed during TC39

[v8-users] Re: [v8-dev] Intent to ship: Private class fields

LGTM On Wed, Feb 20, 2019 at 8:58 PM Sathya Gunasekaran wrote: > Contact Emails > > gsat...@chromium.org > > > Spec > > https://github.com/tc39/proposal-class-fields > > > Summary (taken from our WebFu article > ) > > > > This

Re: [v8-users] Re: Does 'eval' has the same performance as an explicit Script->Compile->Run pipeline?

The document you linked to is outdated. It was based on Crankshaft which hasn't been used since V8 v5.9. See the first two lines: *All this is wrong in TurboFan. (Node 8+)* *Please do not take anything written here as performance advice, this is here for historical reasons.* On Sun, Apr 14,

[v8-users] Re: Intent to Implement: Intl.DisplayNames API Proposal

Can the doc at https://goo.gl/im9wy4 be made public please? Usually we only implement features at stage 3. What’s the motivation for implementing this particular API earlier? (Not saying I’m opposed to it.) *From: *Frank Tang *Date: *Mon, May 13, 2019 at 9:43 PM *To: *v8-users, blink-dev, Adam

Re: [v8-users] Intent to Implement: "numberingSystem" option for Intl.NumberFormat / "calendar" and "numberingSystem" option for Intl.DateTimeFormat

LGTM *From: *Frank Tang *Date: *Tue, May 14, 2019 at 5:33 PM *To: *blink-dev, v8-users, , Adam Klein, Sathya Gunasekaran, Jakob Kummerow, Nebojša Ćirić Contact emails ft...@chromium.org,js...@chromium.org Explainer > https://github.com/tc39/ecma402/pull/175 Design docs/spec Specification: >

[v8-users] Re: [blink-dev] Intent to Remove: 'getThis' and 'getFunction' from the CallSite API

Non-Blink owner LGTM. As Simon points out, Error.prepareStackTrace is non-standard, and so I'm in favor of removing as much from it as we can. On Tue, Jul 2, 2019 at 6:15 PM 'Simon Zünd' via blink-dev < blink-...@chromium.org> wrote: > Contact emails szu...@chromium.org Summary A callback

Re: [v8-users] Re: [v8-dev] Intent to Ship: Promise.allSettled

LGTM On Wed, Apr 24, 2019 at 6:01 AM 'Benedikt Meurer' via v8-dev < v8-...@googlegroups.com> wrote: > LGTM! > > On Wed, Apr 24, 2019, 02:05 Adam Klein wrote: > >> LGTM! >> >> On Tue, Apr 23, 2019 at 4:19 PM Sathya Gunasekaran >> wrote: >> >>> Contact Emails: >>> gsat...@chromium.org >>> >>>

[v8-users] Re: [v8-dev] Re: [blink-dev] Intent to Ship: Promise.{all, race, allSettled} optimization

Non-API owner LGTM. Optimize all the things! On Thu, Apr 25, 2019 at 8:47 PM Adam Klein wrote: > Non-API owner LGTM, as this is a very low-risk change. Its only expected > impact will be a performance improvement/simplification. > > And a reminder to API owners to look at this, since we've just

Re: [v8-users] V8 Regex Optimizations

We recently posted an article detailing some recent improvements: https://v8.dev/blog/regexp-tier-up On Wed, Oct 23, 2019 at 5:12 PM Joel Scarfone wrote: > Hi! > > I'm looking for details on how v8's regular expression optimizations work > under the covers, and if there might be something to