time to trim mustache
khs4473 at gmail.com
Fri Jun 1 08:52:02 PDT 2012
I agree with your sentiments on the usefulness of mustache with respect to
"extending" an object, but I think the point that brings it down is the
fact that it will confuse developers with the put/define distinction. It
just looks too much like batch assignment.
Cascade (or the more specific batch-assignment) would be useful, but
whether the gain in usefulness is worth the added language complexity is
something that would need to be quantified. My hunch is that batch
assignment would only provide a minor improvement.
Regarding super references outside of class bodies: I agree with Luke that
this is a foot gun. The class body provides an easy to understand meaning
for super. Outside of the class body, that meaning is going to be subtle,
probably too subtle to be worth it. When adding methods to objects, we can
always just create an explicit variable to hold the "super" reference.
Regarding private names: I'm not convinced that private, non-reflective
names are unproblematic in and of themselves. I would personally like to
see more exploration on this front, with concrete use-cases. What useful
things can we do with private names that we cannot do with globally unique
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the es-discuss