Niko Matsakis
Niko Matsakis
Now, if we DO introduce a name like `Struct`, then of course we could still keep the metaclass `StructType`, and just have `Struct.prototype === StructType.prototype.prototype` :)
Update: `Array.__proto__ === Function.prototype`, so I would expect `Struct.__proto__` to be the same. This also ensures that `Point instanceof Function`, right? I need to make a diagram!
cc @sebmarkbage
Not written yet.
On Thu, Aug 21, 2014 at 01:24:04PM -0700, Brendan Eich wrote: > You do not want lexical-only suffix resolution, it will make trouble with code that uses i, u, L,...
On Thu, Aug 28, 2014 at 09:24:58AM -0700, Brendan Eich wrote: > The _i convention is anti-usable. JS has to compete, both batteries included (f for float32, L and UL...
@CoDEmanX the order IS guaranteed for object literals, iirc.
Was just checking with @dherman. He clarified that the _intention_ of ES6 was to fully specify the order in those cases, but that it was something we ought to revisit...
So, @tschneidereit, and I worked through this in some detail recently. Our conclusion was that things ultimately worked more smoothly if we retained the "embedded by default" style of the...
@phpnode what I had always assumed we would do is create "incomplete" struct types: ``` js const Tree = new StructType(); ``` The only thing you can legally do with...