Allen, as developer, being unable to `shallow-copy` in JavaScript for other *N* years is actually critical.
Luckily it's not so difficult to polyfill but if you have Rick presenting [something like this]( https://gist.github.com/WebReflection/9353781#objectgetownpropertydescriptorso) I really hope there would be an exception or at least a remote possibility it'd squeeze in :-) I'd be very happy in any case if considered for the future. Once again, a huge thanks for Rick effort and André too helping with the simplified yet more accurate version of the proposal. Best Regards On Tue, Mar 4, 2014 at 10:31 AM, Allen Wirfs-Brock <al...@wirfs-brock.com>wrote: > > On Mar 4, 2014, at 10:17 AM, Rick Waldron wrote: > > >> >> I like this cloning idiom, but I don't see why we would consider this for >> ES6, it isn't something that is critical or can't be implemented via ES >> code. It would be much more appropriate to queue it up for the 2015 train. >> >> ES6: let's wrap this sucker up! >> > > I agree with this, but time permitting I want to at least get something > presented. > > > Presenting is cool, actually necessary to get in on the next train. But > unless something is really critical, let's not try to squeeze it into ES6 > > Allen > > >
_______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
