Re: [w3c/webcomponents] Returning a Proxy from a Custom Element constructor (#857)

Yes, I think we’re on the same page now regarding what I was referring to as a leak.

What can be achieved with only an inherited proxy is limited, yeah; I wasn’t sure whether that recipe would do you any good or not. Proxies don’t afford anything that an ordinary object’s internal methods would not have — even a platform-defined exotic object couldn’t bypass that, it’s the signature of the real internal [[HasProperty]] — but then, they wouldn’t need to, since they could make the instance itself exotic instead.

Looking at your use of proxies in that lib, I’d note that you can achieve run-multiple-real-constructors-with-one-instance without using proxies if it’s okay to require those constructors to extend a special meta class. But I didn’t dig in too far, so I’m not sure what other stuff proxies may be facilitating for this lib.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/857#issuecomment-560027629

Received on Saturday, 30 November 2019 22:52:00 UTC