FWIW, http://www.slideshare.net/BrendanEich/value-objects2 … -- ultra-dense, full-throttle-declarative future-space roadmap shotgunning. IMHO it helps to do early in TC39.
-
-
Replying to @BrendanEich
Next iteration (March mtg, I hope) will focus on "maximally minimal" API, syntactic (lexical grammar) changes to support operators+suffixes.
1 reply 0 retweets 0 likes -
Replying to @BrendanEich
Numeric literal suffix idea, discussed before but revivied by
@nikomatsakis: allow 42L in JS, transpose to L(42), maybe map 'L' to 'int64'.2 replies 0 retweets 0 likes -
Replying to @BrendanEich
. Some back-compat pain to-do with 'in' as suffix (for (var x=0in y); is legal JS, can you dig it?). Also want hex {u,}int64.
@nikomatsakis2 replies 0 retweets 0 likes -
-
Replying to @nikomatsakis
@nikomatsakis Not bad. I think 0L, 40pt, 10mm want a lookup-table from 'L', 'pt', 'mm', etc., to maker function names ('L' => 'int64', &c.).1 reply 0 retweets 0 likes
@BrendanEich such short names invite accidental shadowing as well.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.