Proxy.isProxy (Was: using Private name objects for declarative property definition.)
gal at mozilla.com
Wed Jul 13 12:24:29 PDT 2011
> There are various ways that implementation details can get exposed. For example, by toString'ing a method property. I don't see why isProxy is any more of an abstraction leak than toString. It is actually less, if we clearly position it as one of the meta-programming functions that are available via the Proxy module.
I think this is a very weak argument. Just because we already have one leaky abstraction (toString) doesn't mean we should add additional ones. I prefer moving into the opposite direction: fix toString.
More information about the es-discuss