[v8-users] Re: [blink-dev] Intent to Ship: Intl.DisplayNames

2020-01-06 Thread PhistucK
It is pending review, so not going to stage 3 just yet. ☆*PhistucK* On Mon, Jan 6, 2020 at 8:07 PM Frank Tang wrote: > > > On Mon, Jan 6, 2020 at 10:05 AM Frank Tang wrote: > >> >> >> On Sun, Jan 5, 2020 at 11:21 PM Yoav Weiss wrote: >> >>> >

Re: [v8-users] Re: [blink-dev] Re: Intent to Implement: JavaScript Optional Chaining

2019-09-06 Thread PhistucK
Is this intentionally not an intent to implement and ship, by the way? ☆*PhistucK* On Mon, Aug 12, 2019 at 7:32 PM 'Gabriel Giannattasio' via blink-dev < blink-...@chromium.org> wrote: > This is a great feature to add, looking forward to seeing it in production > :) >

[v8-users] Re: [blink-dev] Re: Intent to Implement: JavaScript Optional Chaining

2019-08-07 Thread PhistucK
ctions. ☆*PhistucK* On Wed, Aug 7, 2019 at 2:56 AM Boris Zbarsky wrote: > On 8/6/19 5:55 PM, Gus Caplan wrote: > > Firefox: Public support ( > https://bugzilla.mozilla.org/show_bug.cgi?id=1566143) > > For what it's worth, there are no signals from Mozilla in that bug &

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

2019-05-15 Thread PhistucK
Thank you for your thoughts, all. I filed an issue with HTML - https://github.com/whatwg/html/issues/4630 ☆*PhistucK* On Wed, May 15, 2019 at 10:52 PM Shane Carr wrote: > Hi PhistucK, > > Thanks for the feedback! Adding HTML for Intl features would be out of > scope for this

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

2019-05-13 Thread PhistucK
- State/province: ☆*PhistucK* On Tue, May 14, 2019 at 5:03 AM Frank Tang wrote: > > > On Mon, May 13, 2019 at 6:56 PM 'Frank Tang (譚永鋒)' via v8-dev < > v8-...@googlegroups.com> wrote: > >> >> >> *From: *Mathias Bynens >> *Date: *Mo

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

2018-12-14 Thread PhistucK
Can you make the example clearer? ["...", index: 0, input: "..."] is unfamiliar, invalid syntax. ☆*PhistucK* On Fri, Dec 14, 2018 at 2:19 AM Peter Wong wrote: > Contact emails > peter.wm.w...@gmail.com > jgru...@chromium.org > yang...@chromium.org > > m

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

2018-10-17 Thread PhistucK
Are the specification and implementation compatible with the Babel based implementation/interpretation of the feature? After all, previously transpiled code could now be interpreted natively... Unfortunately, this is also considered "Web compatibility". ☆*PhistucK* On Wed, Oct 17, 201

[v8-users] Re: [blink-dev] Intent to Implement and Ship: rename Intl.DateTimeFormat.prototype.formatToParts type "dayperiod" to "dayPeriod"

2018-09-06 Thread PhistucK
Great catch goes to han.guokai@ which filed the original issue. :) By the way, all of the pull requests were merged, so mostly accidentally old code would be broken at this point (unless new cases were added since then :(). I will work on the change list again soon. ☆*PhistucK* On Thu, Sep 6

[v8-users] Re: [blink-dev] Intent to Implement and Ship: rename Intl.DateTimeFormat.prototype.formatToParts type "dayperiod" to "dayPeriod"

2018-08-07 Thread PhistucK
Comments inline. ☆*PhistucK* On Wed, Aug 8, 2018 at 3:29 AM Adam Klein wrote: > Apologies for the delay, this got hidden from me due to some gmail > filtering issues...comments inline. > > On Thu, Jul 26, 2018 at 2:14 PM PhistucK wrote: > >> I misremembered formatTo

[v8-users] Re: [blink-dev] Intent to Implement and Ship: rename Intl.DateTimeFormat.prototype.formatToParts type "dayperiod" to "dayPeriod"

2018-07-31 Thread PhistucK
Thoughts, anyone? ☆*PhistucK* On Fri, Jul 27, 2018 at 12:13 AM PhistucK wrote: > I misremembered formatToParts as a relatively recent feature, but now I > see that the intent I remembered was actually discussing NumberFormat. > DateTimeFormat did not seem to have an intent on blink-d

[v8-users] Re: [blink-dev] Intent to Implement and Ship: rename Intl.DateTimeFormat.prototype.formatToParts type "dayperiod" to "dayPeriod"

2018-07-26 Thread PhistucK
tion to add a use counter to V8? Is there an existing use counter for formatToParts altogether that I may have missed (or maybe it is internal)? Also, Node does not have to use V8 anymore, just saying. ;) ☆*PhistucK* On Thu, Jul 26, 2018 at 7:59 PM Adam Klein wrote: > +Jungshik and Da

[v8-users] Re: [blink-dev] Intent to Implement and Ship: rename Intl.DateTimeFormat.prototype.formatToParts type "dayperiod" to "dayPeriod"

2018-07-20 Thread PhistucK
Yep, I know. No rush. ☆*PhistucK* On Fri, Jul 20, 2018 at 9:24 PM Chris Harrelson wrote: > > > On Fri, Jul 20, 2018 at 10:00 AM PhistucK wrote: > >> Guess so, though I am personally not going through with the change if >> there are any blink-dev reservations. ;) >

[v8-users] Re: [blink-dev] Intent to Implement and Ship: rename Intl.DateTimeFormat.prototype.formatToParts type "dayperiod" to "dayPeriod"

2018-07-20 Thread PhistucK
Guess so, though I am personally not going through with the change if there are any blink-dev reservations. ;) ☆*PhistucK* On Fri, Jul 20, 2018 at 7:55 PM Philip Jägenstedt wrote: > This is an FYI for blink-dev, right? Should I remove it from > https://bit.ly/blinkintents? > > On

[v8-users] Intent to Implement and Ship: rename Intl.DateTimeFormat.prototype.formatToParts type "dayperiod" to "dayPeriod"

2018-07-20 Thread PhistucK
ps://chromium-review.googlesource.com/c/v8/v8/+/1145304 Link to entry on the feature dashboard <https://www.chromestatus.com/> https://www.chromestatus.com/features/5252265900244992 Requesting approval to ship? Yes. I think so. Do you think a deprecation period is warranted? There is no (publi

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

2018-02-16 Thread PhistucK
ions from them are not a given (not as far as "strongly positive"). I think it makes sense to add links for opinions that are not your own. Just my two or three cents. ☆*PhistucK* On Fri, Feb 16, 2018 at 3:07 PM, Mathias Bynens wrote: > Note that since this is a V8/JS feature, t

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

2018-02-16 Thread PhistucK
(At least on blink-dev) "Interoperability risk" should have links for citing each vendor and web developer support. ☆*PhistucK* On Fri, Feb 16, 2018 at 2:15 PM, Mathias Bynens wrote: > > > > > > > > > > *Contact emailsmath...@chromium.org > Spechtt

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

2018-01-31 Thread PhistucK
> and Edge ships this anyway I wonder whether those specific Microsoft products even support Edge. Hunch? No. I think this should be shipped regardless. It feels like a low-ransom hostage situation. :P ☆*PhistucK* On Thu, Feb 1, 2018 at 3:18 AM, Rick Byers wrote: > Yay! > Given th

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

2017-06-21 Thread PhistucK
Will it be a lot of effort to just run the tests and create a list of failures? I can go over a manageable part of them and see if something looks fishy. ☆*PhistucK* On Wed, Jun 21, 2017 at 9:07 PM, wrote: > I expect a significant number of tests will fail due to the different > sem

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

2017-06-21 Thread PhistucK
Since this (intent) is a big feature, I think it would be appropriate to run the entire suite in a module scope before it is shipped. Do you think it would take a lot of work to do that? ☆*PhistucK* On Wed, Jun 21, 2017 at 8:27 PM, Adam Klein wrote: > On Wed, Jun 21, 2017 at 9:44 AM, Phist

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

2017-06-21 Thread PhistucK
On Wed, Jun 21, 2017 at 6:25 PM, Domenic Denicola wrote: >

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

2017-06-21 Thread PhistucK
the same engine, but who knows, it may uncover hidden peculiarities in the engine) ☆*PhistucK* On Wed, Jun 21, 2017 at 6:54 PM, Adam Klein wrote: > On Wed, Jun 21, 2017 at 8:25 AM, Domenic Denicola wrote: > >> From: blink-...@chromium.org [mailto:blink-...@chromium.org] On

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

2017-06-21 Thread PhistucK
Since there is no intent-to-ship-modules thread in V8 (and since this intent brings module support into HTML as well as scripts and not just one or the other), I think the test262 question is very much appropriate in this thread (you may disagree, but I may, too ;)). ☆*PhistucK* On Wed, Jun 21

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

2017-06-20 Thread PhistucK
that signals that the fetch event is for a module fetch? ☆*PhistucK* -- -- 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 gr

[v8-users] Re: [blink-dev] Intent to Ship: Object rest/spread properties

2017-04-29 Thread PhistucK
around 2001, so not a novice by definition.) ☆*PhistucK* On Sun, Apr 30, 2017 at 6:02 AM, kai zhu wrote: > i apologize if this is not the most appropriate mailing list, but i can’t > help but express my frustration at the chaos in frontend-world caused by > over-abuse of all the new es

[v8-users] Re: [blink-dev] Intent to Ship: Object rest/spread properties

2017-04-27 Thread PhistucK
Cool, thank you and sorry! ☆*PhistucK* On Thu, Apr 27, 2017 at 6:20 PM, Jeffrey Yasskin wrote: > Stage 3 is exactly the stage at which implementations are supposed to > ship: https://tc39.github.io/process-document/, in particular the > entrance criteria for stage 4 requi

[v8-users] Re: [blink-dev] Intent to Ship: Object rest/spread properties

2017-04-27 Thread PhistucK
Is it fine to ship it as it is a stage 3 proposal at the moment? See tc39/proposals <https://github.com/tc39/proposals>. ☆*PhistucK* On Fri, Apr 21, 2017 at 12:04 AM, Adam Klein wrote: > Thanks, LGTM to ship! > > On Thu, Apr 20, 2017 at 12:38 PM, Sathya Gunasekaran > wrote

[v8-users] Re: [blink-dev] Intent to ship: Trailing comma in JavaScript function parameter lists

2017-01-13 Thread PhistucK
build​. So the situation is the same as with WebKit and Gecko. I really do not like this feature (why does C++ exclude this?)... JavaScript is loose enough as it is, but this is not the place for such feedback. :) ☆*PhistucK* -- -- v8-users mailing list v8-users@googlegroups.com http://groups.googl

Re: [v8-users] Breaking On Native Function Calls

2016-10-19 Thread PhistucK
Yes, I am. I already noticed it is blocking the Chromium issue. Thank you! ☆*PhistucK* On Thu, Oct 20, 2016 at 9:33 AM, Yang Guo wrote: > I guess you are looking for https://bugs.chromium.org/ > p/v8/issues/detail?id=178 > > This is a long standing feature request that has not be

Re: [v8-users] Breaking On Native Function Calls

2016-10-19 Thread PhistucK
Yeah, I wish. I do not have a strong machine yet. :( I wanted to try an old version of Chromium (which does not have [Unforgeable] yet), but my corporate proxy is blocking me from using the site in question. I will try again when I am home. ☆*PhistucK* On Thu, Oct 20, 2016 at 9:31 AM

Re: [v8-users] Breaking On Native Function Calls

2016-10-19 Thread PhistucK
File ​crbug.com/657697​ (and crbug.com/657700 for a related bug I found as a result :(). But it is really a duplicate of crbug.com/49 (so I closed mine). I guess it will not be in progress soon. :( ☆*PhistucK* On Thu, Oct 20, 2016 at 8:19 AM, Jochen Eisinger wrote: > As far as I k

[v8-users] Breaking On Native Function Calls

2016-10-19 Thread PhistucK
I wanted to know whether there is a V8 (or Chrome) flag of some sort that will let me add breakpoints on native function calls. I do not mean C++ functions, I mean built in web platform (or ECMAScript) functions. My issue is that I click on a link and suddenly some code is apparently calling doc

Re: [v8-users] Re: Disabling All Of The Optimizations

2016-09-26 Thread PhistucK
ich is not ideal... ☆*PhistucK* On Mon, Sep 26, 2016 at 9:42 AM, Jochen Eisinger wrote: > Thanks for tracking this down. In general, if you're willing / able to > provide a repro case, we're happy to investigate suchs bugs ourselves, so > you don't have to go through the

Re: [v8-users] Re: Disabling All Of The Optimizations

2016-09-25 Thread PhistucK
d have reported it if it did not require days of investigations). ☆*PhistucK* On Sat, Sep 24, 2016 at 1:45 PM, PhistucK wrote: > Thank you! Unfortunately, for everyone, it is getting clearer and clearer > that this is an optimization issue. The issue does not reproduce with the > --no-

[v8-users] Re: Disabling All Of The Optimizations

2016-09-24 Thread PhistucK
nd the exact issue (without showing code :()? ☆*PhistucK* On Tuesday, September 20, 2016 at 3:54:19 PM UTC+3, Michael Hablich wrote: > --no-crankshaft should do the trick. The name is misleading, it will also > disable TurboFan. > > On Tuesday, September 20, 2016 at 1:51:51 PM UTC+2,

[v8-users] Disabling All Of The Optimizations

2016-09-20 Thread PhistucK
I have an issue where the code suddenly (since Chrome 53) gets caught up in a cyclic recursion until it exceeds the stack size limit. Since the code is the same, I want to try and rule out engine optimization issues. Is there a V8 flag for disabling all of the optimizations? ☆*PhistucK

[v8-users] Re: [blink-dev] Re: Intent to implement async/await functions

2016-05-30 Thread PhistucK
So which one should be removed? Can you merge their content in a reasonable way and remove one of them? ☆*PhistucK* On Tue, May 31, 2016 at 1:29 AM, Caitlin Potter wrote: > LGTM1 (just kidding) > > Sorry for not getting the launch process ball rolling myself months ago, > that pro

[v8-users] Re: [blink-dev] Re: Intent to implement async/await functions

2016-05-28 Thread PhistucK
I love this. By the way, why are there two ChromeStatus entries? https://www.chromestatus.com/feature/5644533144485888 as well as https://www.chromestatus.com/feature/5643236399906816? ☆*PhistucK* On Thu, May 12, 2016 at 6:34 PM, wrote: > Super excited for this to land in V8, and then

[v8-users] Re: [blink-dev] Re: Passive Error Event

2016-05-27 Thread PhistucK
Of course listening to the event is implemented in Blink, but it uses V8 APIs in order to break at uncaught exceptions, so I wondered if activating this makes the execution less performant. ☆*PhistucK* On Fri, May 27, 2016 at 6:19 PM, Yang Guo wrote: > That doesnt sound like something in

[v8-users] Re: [blink-dev] Re: Passive Error Event

2016-05-24 Thread PhistucK
Not throwing errors, but whether adding an event listener to the "error" influences performance without even throwing errors. I just do not know... ☆*PhistucK* On Tue, May 24, 2016 at 1:46 PM, Yang Guo wrote: > Throwing errors typically are not and should not be on the critical

[v8-users] Passive Error Event

2016-05-19 Thread PhistucK
ome way (for example, fire it not immediately if it knows there is more code to run at the moment, or something similar, batching and so on)? Again, I do not know whether there is even any performance implication to adding an "error" event listener, you probably know more. Just an idea.

[v8-users] Re: [blink-dev] Re: Intent to Ship: Object.values() and Object.entries()

2016-05-03 Thread PhistucK
Thank you. :) ☆*PhistucK* On Tue, May 3, 2016 at 7:45 PM, Caitlin Potter wrote: > V8 passes all of the relevant test262 tests included in the current > test262 roll. > > Regarding interop, there's a bug in the current FireFox implementation (so > they do not to

[v8-users] Re: [blink-dev] Re: Intent to Ship: Object.values() and Object.entries()

2016-05-03 Thread PhistucK
Are the implementations interoperable? Does V8 pass all of the relevant test262 tests? (By the way, I suggest adding these questions to the standard V8 intent template) ☆*PhistucK* On Tue, May 3, 2016 at 7:21 PM, Caitlin Potter wrote: > It's in v8-users, here's a copy :x >

[v8-users] Re: [blink-dev] Re: Intent to Ship: Object.values() and Object.entries()

2016-05-03 Thread PhistucK
The post itself seems to be missing. :( ☆*PhistucK* On Tue, May 3, 2016 at 7:13 PM, Caitlin Potter wrote: > +blink-dev >> >> -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group

[v8-users] Re: [blink-dev] Re: Intent to Un-ship: Object.observe

2016-02-23 Thread PhistucK
His message actually stated it will be removed, not deprecated, in Chrome 50. ☆*PhistucK* On Tue, Feb 23, 2016 at 5:41 PM, 'Joe Medley' via blink-dev < blink-...@chromium.org> wrote: > Adam, > > Just to clarify, it sounds like this isn't being deprecated in M49, b

[v8-users] Blog Post Correction

2015-12-03 Thread PhistucK
12/chrome-48-beta-present-to-cast-devices_91.html> ? V8 people, please, holler if this is incorrect. Thank you! ☆*PhistucK* -- -- 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

Re: [chromium-discuss] Re: [v8-users] No Garbage Collection For Hours

2015-10-07 Thread PhistucK
Windows 7. ☆*PhistucK* On Wed, Oct 7, 2015 at 4:51 PM, Jochen Eisinger wrote: > depends a bit on the OS you run chromium on? > > On Mon, Oct 5, 2015 at 6:55 PM PhistucK wrote: > >> Sure, but how do I get the output of the extension process? By enabling >> logg

[v8-users] Re: [blink-dev] Intent to Implement: SIMD.js

2015-10-07 Thread PhistucK
Is this in development? ☆*PhistucK* On Thu, May 7, 2015 at 3:00 AM, 'Bill Budge' via blink-dev < blink-...@chromium.org> wrote: > # Contact Info > bbu...@chromium.org, bradnel...@chromium.org > > # TC39 acceptance > > SIMD.js is a proposal in ES7 > htt

Re: [chromium-discuss] Re: [v8-users] No Garbage Collection For Hours

2015-10-05 Thread PhistucK
Sure, but how do I get the output of the extension process? By enabling logging? ☆*PhistucK* On Mon, Oct 5, 2015 at 12:52 PM, Jochen Eisinger wrote: > it would be interesting to have the output of the extension process when > running chromium with --js-flags="--trace-gc --t

[v8-users] No Garbage Collection For Hours

2015-10-03 Thread PhistucK
or a Chromium issue? I figure it is a V8 issue, but I want to make sure, since it does involve extensions (a background page) and DOM operations. ☆*PhistucK* -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because yo

Re: [blink-dev] Re: [v8-users] Intent to ship: ES6 Template Literals

2014-12-17 Thread PhistucK
Oh, right. I get it now, thank you! ☆*PhistucK* On Wed, Dec 17, 2014 at 9:15 PM, 'Erik Arvidsson' via blink-dev < blink-...@chromium.org> wrote: > > With String.raw `\n` you get "\\n" versus with `\n` you get "\n". > > On Wed, Dec 17, 2014 at 2:

Re: [blink-dev] Re: [v8-users] Intent to ship: ES6 Template Literals

2014-12-17 Thread PhistucK
and it is supposed to be String.raw("bla\n${5+6}")? ☆*PhistucK* On Wed, Dec 17, 2014 at 7:31 PM, Joshua Bell wrote: > > Any caveats? > > Does this include the use of tags (i.e. tag`literal`;) ? > > Does this include String.raw()? > > (IMHO a subset w/o

Re: [v8-users] Re: [blink-dev] Intent to ship: ES6 String functions

2014-11-27 Thread PhistucK
Then I guess I am also looking to help educate about new platform features. I understand this use case is much less needed, though. ☆*PhistucK* On Thu, Nov 27, 2014 at 9:52 PM, Dmitry Lomov wrote: > > > On Thu, Nov 27, 2014 at 8:48 PM, PhistucK wrote: > >> Well, you got th

Re: [v8-users] Re: [blink-dev] Intent to ship: ES6 String functions

2014-11-27 Thread PhistucK
ecently added to the platform and was overridden by this website. If you expect the standard variation of this method, perhaps polyfill it only when it does not exist. String.prototype.includes was recently added to the platform and used by this website. If you see issues, consider this as a possible c

[v8-users] Re: [blink-dev] Intent to ship: ES6 String functions

2014-11-27 Thread PhistucK
*exist 'contains' is the obvious choice, 'includes' is not. This is what I mean. While 'contains' is better named, 'includes' is less risky and therefore should be chosen. I am finally done, I think. Sorry for the triple post. ☆*PhistucK* On Thu,

[v8-users] Re: [blink-dev] Intent to ship: ES6 String functions

2014-11-27 Thread PhistucK
*shortcut My last message was probably confusing, so continuing it - By that, I mean that it makes more sense for 'contains' to exists already on the web, than for 'includes'. ☆*PhistucK* On Thu, Nov 27, 2014 at 1:55 PM, PhistucK wrote: > This is very debateable,

[v8-users] Re: [blink-dev] Intent to ship: ES6 String functions

2014-11-27 Thread PhistucK
This is very debateable, really. To me, it makes sense (and in my experience, also exists) that "contains" makes more sense (as a shortcuts for return this.indexOf(str) !== -1) than 'includes'. ☆*PhistucK* On Thu, Nov 27, 2014 at 1:52 PM, Philip Jägenstedt wrote: > On

Re: [v8-users] Re: [blink-dev] Intent to ship: ES6 String functions

2014-11-27 Thread PhistucK
This is to ease debugging, not to solve every single case. As much as possible, log it. On a 'best available' case. ☆*PhistucK* On Thu, Nov 27, 2014 at 1:14 PM, 'Andreas Rossberg' via blink-dev < blink-...@chromium.org> wrote: > On 27 November 2014 at 11:39, Dm

[v8-users] Re: [blink-dev] Intent to ship: ES6 String functions

2014-11-27 Thread PhistucK
Can we add a console log (not a warning) for the canary/dev/beta run (perhaps stable, too?) for a little while to aid developers with possible breakages? If String.prototype.includes is overridden, deleted or accessed (called or gotten), the log would be printed. ☆*PhistucK* On Thu, Nov 27

[v8-users] Re: [blink-dev] Intent to ship: ES6 generator functions (V8)

2014-09-19 Thread PhistucK
Thank you for sharing! Exciting, I know a lot of developers have been waiting for it. Hopefully Internet Explorer and Safari implements them soon enough as well. Do you intend to ship it with the referenced issues, or is the plan to fix them before shipping (preferred, obviously)? ☆*PhistucK

[v8-users] Re: [blink-dev] Re: V8 Intent to implement: ES6 classes

2014-08-18 Thread PhistucK
Yes, stagnation is much better! ?! ☆*PhistucK* On Mon, Aug 18, 2014 at 10:25 AM, newghost wrote: > > V8 become more and more complex. > > > On Friday, August 15, 2014 4:46:39 PM UTC+8, Dmitry Lomov wrote: >> >> Implement ES6 classes including: >&

[v8-users] Re: Symbol Support

2014-08-15 Thread PhistucK
(Sorry for the delayed reply, I apparently opted out of getting e-mails to threads I start. Weird) Great, thank you! I updated the article a bit with the compatibility data (for Opera as well) and removed the false Symbol.prototype.name bit. ☆*PhistucK* On Tuesday, August 12, 2014 11:30:37

[v8-users] Symbol Support

2014-08-12 Thread PhistucK
t; are supported. Symbol.iterator is supported and now Symbol.unscopables is also supported. What else? Do Symbol.for and Symbol.keyFor do everything they should? It also says Symbol.prototype.name exists only in V8 - was it removed? Thank you! ☆*PhistucK* On Thu, Aug 7, 2014 at 12:16 PM, Andy Wingo

Re: [v8-users] Re: [blink-dev] Intent to ship: ES6 iteration (for-of)

2014-08-07 Thread PhistucK
Since this matches Firefox and Internet Explorer is already developing <http://status.modern.ie/jsiteratorsietheforoffeature?term=for-> the feature, shipping this looks great to me. :) One step closer to ECMAScript 6! Yay. ☆*PhistucK* On Thu, Aug 7, 2014 at 12:52 PM, Andy Wingo wrote:

[v8-users] Re: [blink-dev] Intent to ship: ES6 iteration (for-of)

2014-08-07 Thread PhistucK
(throwing is not very nice to feature detect)? ☆*PhistucK* On Thu, Aug 7, 2014 at 12:16 PM, Andy Wingo wrote: > For-of ("for (x of iterable) {}") is a part of ES6 [1]. > > For-of has been shipping in Firefox since version 27 (February 2014) > [2]. IE and Safari deve

Re: [blink-dev] Fwd: [v8-users] Intent to ship ES6 promises & weak collections

2014-03-21 Thread PhistucK
e only intents to ship) - https://groups.google.com/forum/#!searchin/v8-users/subject$3Aintent%7Csort:date ☆*PhistucK* On Thu, Mar 20, 2014 at 11:46 AM, Jochen Eisinger wrote: > FYI - V8 promises will be enabled hopefully for M35. The v8 implementation > was updated to reflect the Ja

[v8-users] Re: [chromium-dev] Re: [blink-dev] Re: V8 Launch Process and Guidelines

2013-09-16 Thread PhistucK
announcements (VP9) exist (mostly, but at least that). Announcements, though, not intents, which is a shame. ☆*PhistucK* On Mon, Sep 16, 2013 at 6:23 PM, Mike Frysinger wrote: > Chromium isn't really part of the "web platform". it's the chrome around > the web plat

[v8-users] Re: [chromium-dev] Re: [blink-dev] Re: V8 Launch Process and Guidelines

2013-09-16 Thread PhistucK
ses it. It exposes stuff to the web platform under non transparent, non public guidelines. ☆*PhistucK* On Mon, Sep 16, 2013 at 6:34 PM, Mike Frysinger wrote: > which isn't relevant. if you want to talk about standardization of the > NaCl/PNaCl projects, then you should start threads o

[v8-users] Re: [chromium-dev] Re: [blink-dev] Re: V8 Launch Process and Guidelines

2013-09-16 Thread PhistucK
Right, but Chromium exposes them to the web platform, not Blink. ☆*PhistucK* On Mon, Sep 16, 2013 at 6:31 PM, Mike Frysinger wrote: > NaCl/PNaCl are sep projects. they would run their own guidelines > independently of Chromium. > -mike > > > On Mon, Sep 16, 2013 at 11:28 A

[v8-users] Re: [blink-dev] Re: V8 Launch Process and Guidelines

2013-09-16 Thread PhistucK
Only Chromium itself is left, right? :) ☆*PhistucK* On Mon, Sep 16, 2013 at 5:15 PM, Alex Komoroske wrote: > Thanks for sharing, Dmitry! > > Blink is just one of the sub-projects of Chromium that have web-developer > facing features, and it's great to see other sub-projects

[v8-users] Re: [blink-dev] V8 Launch Process and Guidelines

2013-09-16 Thread PhistucK
Not transparent quite yet - that link is not public and there is no summary. ;) ☆*PhistucK* On Mon, Sep 16, 2013 at 12:41 PM, Dmitry Lomov wrote: > Following the lead of Blink in setting the web platform guidelines, we on > the V8 team came up with a similar set of guidelines specific

Re: [v8-users] Parse\Runtime Issues

2011-01-28 Thread PhistucK
This makes everything much clearer. Thank you very much for your time. ☆*PhistucK* On Fri, Jan 28, 2011 at 15:22, Lasse R.H. Nielsen wrote: > If and else are not two statements. It's two different forms of the > if-statement. > > The if statement is a compound statement, me

Re: [v8-users] Parse\Runtime Issues

2011-01-28 Thread PhistucK
I recently found out you can actually run this code without any error - if (some_condition) some_function(); else some_other_function(); ☆*PhistucK* 2011/1/28 Mikael Helbo Kjær > Hi there. > > > > This is not the usual thing to ask here (I’d go for some sort of Javascript >

Re: [v8-users] Parse\Runtime Issues

2011-01-28 Thread PhistucK
Thank you for the very quick reply! Got it, I think.. well, not entirely. Which is why I am asking regarding the second code (without the semicolon) I posted in the original message. Can you, please, clarify the behavior of the second code I posted? ☆*PhistucK* On Fri, Jan 28, 2011 at 14:15

Re: [v8-users] Parse\Runtime Issues

2011-01-28 Thread PhistucK
I am trying it within Chromium. I posted it to v8-users, because it is a JavaScript issue, rather than a rendering issue. The syntax error does not show up on Internet Explorer 8. It does, however, show up on Internet Explorer 9 (one of the platform previews). ☆*PhistucK* On Fri, Jan 28, 2011

[v8-users] Parse\Runtime Issues

2011-01-28 Thread PhistucK
} else { alert("a is not o"); }; Shows an alert - "a is not o". As far as I know, "if" and "else" count as two statements. If they are, the "else" block is actually part of the first "if" statement. Am I misinformed, or is it a bug? Thank you for your time! ☆*PhistucK* -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users

[v8-users] Numeric Key Names In Objects Get Automatically Sorted In V8\Chrome

2010-08-31 Thread PhistucK
and then "282". I have not tested Safari, or anything not on Windows. Is this a bug? Thank you. ☆*PhistucK* -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users