RE: [blink-dev] Re: [v8-users] Intent to Ship: globalThis

2018-09-06 Thread Domenic Denicola
From: Yuki Shiino > +cc: domenic@, what do you think of this, especially from PoV of LAPI? This won't be useful for LAPIs, but that's OK. We need a bigger solution for the general problem of getting un-tamperable original references, and the global object is just one of many objects we'll

[v8-users] RE: [blink-dev] Intent to Ship:

2017-06-21 Thread Domenic Denicola
From: blink-...@chromium.org [mailto:blink-...@chromium.org] On Behalf Of PhistucK > What about test-262 (web-platform-tests are not supposed to test ECMAScript > features) for modules?​ This is not an ECMAScript feature; this is an intent-to-ship specifically for

RE: [v8-users] Trouble running tests on Windows

2015-09-15 Thread Domenic Denicola
From: v8-users@googlegroups.com [mailto:v8-users@googlegroups.com] On Behalf Of Jakob Kummerow > https://code.google.com/p/v8-wiki/wiki/BuildingWithGYP#Running_tests Thanks. I think I had previously tried that but forgotten to change "build" to "out". It would still be ideal if Windows

[v8-users] Trouble running tests on Windows

2015-09-15 Thread Domenic Denicola
I have two persistent issues while trying to run the V8 tests on Windows, and was hoping someone had figured out a workaround: 1. run-tests.py seems to expect output to be in folders named things like out/ia32.debug or out/x64.debug, whereas the Windows build puts them in out/Debug

[v8-users] Named property interceptor interfering with accessor properties on the same object

2015-09-08 Thread Domenic Denicola
could investigate similar fixes in Node.js. From: yukishi...@google.com [mailto:yukishi...@google.com] On Behalf Of Yuki Shiino Sent: Tuesday, September 8, 2015 03:02 To: Domenic Denicola <d...@domenic.me> Cc: blink-dev <blink-...@chromium.org>; Yuki Shiino <yukishi...@chromium.o

[v8-users] Intent to ship: Array.prototype.includes

2015-08-11 Thread Domenic Denicola
The Array.prototype.includes proposal [1] is on track for ES2016 and is currently in stage 3 of the process, awaiting shipping implementations before it can advance to stage 4. It provides a nice way to test for membership in an array (including avoiding edge cases around NaN). Firefox already

Re: [v8-users] How to debug V8 context creation failure in Blink layout tests?

2015-07-02 Thread Domenic Denicola
there? On Wednesday, July 1, 2015 at 5:35:58 PM UTC+9, Jochen Eisinger wrote: Currently, the only thing you can do is to attach a debugger, and see what the exception is that gets thrown. best -jochen On Tue, Jun 30, 2015 at 3:54 PM Domenic Denicola d...@domenic.me javascript: wrote: While

[v8-users] How to debug V8 context creation failure in Blink layout tests?

2015-06-30 Thread Domenic Denicola
While messing around with V8 extras, I managed to introduce some malformed syntax or misused API, which caused V8 context creation to fail during layout test startup. This manifests in WebCoreTestSupport::injectInternalsObject being passed an empty v8::Localv8::Context, and a subsequent crash.

RE: [blink-dev] Re: [v8-users] Intent to ship: ES'15 arrow functions

2015-06-18 Thread Domenic Denicola
How is the test pass rate, using https://github.com/tc39/test262/tree/master/test/language/expressions/arrow-function ? From: blink-...@chromium.org [mailto:blink-...@chromium.org] Sent: Thursday, June 18, 2015 10:39 To: v8-users@googlegroups.com Cc: blink-dev Subject: [blink-dev] Re:

[v8-users] RE: [blink-dev] Intent to implement: V8 extras

2015-05-20 Thread Domenic Denicola
https://docs.google.com/document/d/1AT5-T0aHGp7Lt29vPWFr2-qG8r3l9CByyvKwEuA8Ec0/edit?usp=sharing is now complete, including sections on technical design, security considerations, and alternatives considered that were missing yesterday when I sent the previous message. Comments appreciated! --

[v8-users] RE: [blink-dev] Intent to implement: V8 extras

2015-05-19 Thread Domenic Denicola
(I also want to see a design document of V8 extras.) Your wish is my command! Working on one at https://docs.google.com/document/d/1AT5-T0aHGp7Lt29vPWFr2-qG8r3l9CByyvKwEuA8Ec0/edit?usp=sharing ; got through most of the introductory/scope stuff and have a lot of TODOs for the technical side,

[v8-users] Intent to implement: V8 extras

2015-05-11 Thread Domenic Denicola
, but for example if we were to implement something like TextEncoder or URL as an extra, it would be crucial. Overall though, we are quite excited about the possibilities this opens up, by allowing embedders a performant way to implement features in JavaScript. Best, Domenic Denicola Jochen

RE: [blink-dev] Re: [v8-users] Self-hosted streams in Blink/V8

2015-02-12 Thread Domenic Denicola
]: https://codereview.chromium.org/924713002 -Original Message- From: Domenic Denicola Sent: Monday, February 9, 2015 12:23 To: 'Andreas Rossberg'; v8-users@googlegroups.com Subject: RE: [blink-dev] Re: [v8-users] Self-hosted streams in Blink/V8 From: blink-...@chromium.org [mailto:blink

RE: [blink-dev] Re: [v8-users] Self-hosted streams in Blink/V8

2015-02-09 Thread Domenic Denicola
From: blink-...@chromium.org [mailto:blink-...@chromium.org] This sounds like a reasonable plan. However, can you explain why you think that you need any patch to V8 at all? Well, mainly because I thought it'd be the easiest way to get a proof-of-concept off the ground (i.e. something we

[v8-users] Self-hosted streams in Blink/V8

2015-02-06 Thread Domenic Denicola
I’d like to investigate a proof-of-concept implementation of the streams APIhttp://streams.spec.whatwg.org/ using the same self-hosting techniques that V8 uses for promises. The first stage of this work would be to produce patches to V8 and Blink, without intent of getting the merged, to