> The only thing I find off the mark is the typography of <|. In light of this,
> and of the anti-grawlix reaction among many people, could we revisit an infix
> operator used in restricted productions with [no LineTerminator here] on the
> left of the operator contextual keyword?
I hope this is not just in deference to a few vocal opponents. Valid reasons
for changing the operator are: a majority demands it or the change helps make
it politically viable. I, for one, like the way it looks and find it highly
intuitive: it looks like an arrow. And when I draw object diagrams, I draw
pointers from an object to its prototype.
> Likely keywords include 'proto' (but 'protos' seems better English given the
> LHS being the prototype object), or my current best shot: 'beget'.
>
> let obj = base beget {a: 1, b: 2}
> let arr = base beget [p, q, r]
> let fun = base beget function (...args) { ... }
> let re = base beget /(\w+)\s+(\w)+/g
How about subsumes (as the inverse of “extends”)?
let obj = base subsumes {a: 1, b: 2}
let arr = base subsumes [p, q, r]
let fun = base subsumes function (...args) { ... }
let re = base subsumes /(\w+)\s+(\w)+/g
A bit long, but reads nicely.
--
Dr. Axel Rauschmayer
[email protected]
home: rauschma.de
twitter: twitter.com/rauschma
blog: 2ality.com
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss
