Re: Is there a way to run test262 in a browser (and especially in web workers)?

The current website needs an update. If it makes less painful to run the tests on a shell, you can try https://github.com/bterlson/eshost On Thu, Mar 17, 2016 at 11:34 AM, saam barati wrote: > I use: > http://v8.github.io/test262/website/default.html > > Saam > > On Mar

Re: Is there a way to run test262 in a browser (and especially in web workers)?

I have a little bash script that might help. Let's say you have the folder `~/tests` ... you can prepare the fodler as such. ```sh # go into the folder cd ~/tests # prepare 2 dirs mkdir tmp262 mkdir utils # will take forever ... git clone https://github.com/tc39/test262 ``` Now, while it's

Re: One-shot Delimited Continuations with Effect Handlers

> > Isn't the problem we actually need to solve here the fact we're not able > to control scheduling or context in async functions? > Other languages with async functions like Python and C# provide the means > to control the scheduling of async functions. > Algebraic effects also allows the

Re: stable sort proposal

On Tue, Mar 15, 2016 at 8:50 AM, Vic9 wrote: >> What about the Timsort? > > I cannot believe it will be faster on random int array. And TimSort is base > on MergeSort and, seems, for it's worst cases it cannot be better than > MergeSort. > I have tried

Re: Class and Property Initialization

In my own code I tend to do the constructor/executor pattern: ``` class A { constructor(exec) { this.a = 1; exec(this); Object.freeze(this); } } class B extends A { constructor() { super(() => { this.b = 2; }); } } ``` And it works out pretty well. On Fri, Mar

Re: Class and Property Initialization

> > That said, it has one problem -- base classes. You can't seal them > because the constructor in the extended class would fail (I tried it) > and so the base classes would always have to remain unsealed which > means you either (1) understand that or (2) always use an extended class > if you

Re: Proxy handler.has() does not have a receiver argument?

To be clear, I'm not suggesting behavior like `getOwnPropertyNames` be overridden by anything on the prototype, just a way to use proxies without having to instantiate identical copies that all use the same handler. I still believe a proxy on the prototype should always have a `receiver` sent to

Draft Proposed Standard SES (Secure EcmaScript)

Chip Morningstar and I would like to announce a new proposal, on the agenda for the upcoming March meeting: Draft Proposed Standard SES (Secure EcmaScript) It is now ready for comments at https://github.com/FUDCo/ses-realm Feedback welcome, both here on this list and on that proposal's

Re: stable sort proposal

On 03/18/2016 11:10, Tab Atkins Jr. wrote: If you're planning on pessimistically assuming that legacy implementations use an unstable sort for Array#sort(), then testing for the presence of Array#fastSort() (and assuming that when it appears the Array#sort is stable) is exactly as useful as

Re: Proxy handler.has() does not have a receiver argument?

I think I figured out how to make inheritance work... ```js var wm1 = new WeakMap(); function A() { let proxy = new Proxy(this, { get: (target, property, receiver) => property === 'bacon' || target[property] }); wm1.set(proxy, {}); return proxy; } var wm2 = new WeakMap(); function B() { let proxy

Re: stable sort proposal

On Fri, Mar 18, 2016 at 3:57 PM, Waldemar Horwat wrote: > On 03/18/2016 11:10, Tab Atkins Jr. wrote: >> >> If you're planning on pessimistically assuming that legacy >> implementations use an unstable sort for Array#sort(), then testing >> for the presence of Array#fastSort()