I'm not trying to rule them out. I am simply observing that two tracing proxies that trace differently in front of the same target are not the same. I don't want the kernel equality primitives of my language to lie to me about that. (Fortunately, if we insist that === be fast, then we can't trap it anyway so we don't need to worry about this misrepresentation.)
On Sat, Dec 7, 2013 at 5:37 AM, Jason Orendorff <jorendo...@mozilla.com>wrote: > On 12/6/13 7:00 PM, Sam Tobin-Hochstadt wrote: > > On Wed, Dec 4, 2013 at 5:59 PM, Mark Miller <erig...@gmail.com> wrote: > >> Once we have such an open-ended projection-only abstraction, then all > these > >> questions about equality become interesting and pressing. > > I'm unconvinced that this is genuinely a problem that needs solving. > > In particular, I don't think that given such a projection-only > > abstraction, any of the questions about equality are easier. > > I agree. > > Why are projections more interesting/useful than other variations in > behavior? Why are we supposed to treat them as not being variations? A > projection-only abstraction would rule out tracing proxies, which most > often don't change the behavior observed by code using the proxy in > practice, but permit proxies that conditionally make a request throw, > which surely will be. > > -j > -- Text by me above is hereby placed in the public domain Cheers, --MarkM _______________________________________________ dev-tech-js-engine-internals mailing list dev-tech-js-engine-internals@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
