Note that value object proposal does _not_ address int64.
On Tue, Apr 8, 2014 at 1:27 AM, Waldemar Horwat walde...@google.com wrote:
On 04/02/2014 07:32 AM, Niko Matsakis wrote:
I just wanted to let people on es-discuss know about two of my recent
blog posts concerning typed objects. The
Hello,
The current ES6 draft seems to specify that if a running generator
throws an exception, that its state moves to completed. It seems to
specify this in ยง25.3.3.1, `GeneratorStart'. (Oddly, the procedure
described in `GeneratorResume' can return to `GeneratorStart'; spec
strangeness).
Note that value object proposal does not address int64.
FWIW, I'm too interested in solving the int64 problem somehow. The last I
heard about int64 was here:
http://www.slideshare.net/BrendanEich/value-objects2. How does the int64
story move forward?
--
Cristian Petrescu-Prahova | Software
int64 and uint64 are integral parts of value objects, first proofs of
concept even. Sorry I fell behind on the SpiderMonkey bug, I'm hoping
others will take it over (cc'ed; and for V8) and revive it. It has
obvious use-cases in Node.js and anything that tiles the OS syscall surface.
/be
4 matches
Mail list logo