Good points that we will have to specify careful.  Also one the reasons we do 
prototype implementations.

Such issues seems inherent in the adoption of an intercession API and 
semantics.  Having to deal with such issues isn't really new.  In ES5 we had to 
deal with this possibility WRT [[Get]] and [[Set]] triggering accessors it 
forced us in some cases to use [[DefineOwnProperty]] instead of [[Put]].  The 
impact on the internal methods were relatively small in ES5.  It was larger for 
some of the syntactic production evaluation semantics. The biggest impact was 
on built-ins. I agree that Proxies will have even broader impact and I can even 
imagine that working through them might lead to some refactoring of the 
internal properties in order to reduce such effects.  such refactorings might 
then force some changes in to the Proxy Traps.

more below

On Oct 5, 2011, at 9:57 AM, Andreas Rossberg wrote:

> 
> In summary, I'm slightly worried. The above all seems fixable, but is
> that all? Ideally, I'd like to see a more thorough analysis of how the
> addition of proxies affects properties of the language and its spec.
> But given the state of the ES spec, that is probably too much to wish
> for... :)

I'm not sure what you mean my the last sentence. I have not yet done any work 
to incorporate proxies into the ES6 draft.  What we currently have is proposal 
that does not address this depth of specification.  I can assure you that, we 
will when they start to move into the ES6 draft.

If you have specific issues like these a good way to capture them is to file 
bugs against  the "proposals" component  of the "harmony" products at 
bugs.ecmascript.org.  Proposes resolutions would be good too.  I definitely 
look at reported proposal bugs when I work on incorporating new features into 
the draft specification.  On the other hand I don't guarantee that I will spot 
or remember all issues raised on this list.  So file bugs.

Allen
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss

Reply via email to