Re: partial interfaces, [NoInterfaceObject]

On Fri, Feb 14, 2014 at 7:41 PM, Jonas Sicking <jonas@sicking.cc> wrote:
> There's also a cost for implementations and authors that read the spec
> that there are additional interfaces to juggle. I.e. when you see the
> "interface NavigatorGeolocation { ... }", you have to remember (or
> look up) that there's a "Navigator implements NavigatorGeolocation" to
> know that that API appears on the navigator object. I.e. the
> "implements" add an extra level of indirection which complicates the
> mental model.

Yeah, we could just have partial interface X, Y { }; to solve this.
Seems a lot cleaner. Also, now we have [Exposed] the worker setup
could be much simpler.


-- 
http://annevankesteren.nl/

Received on Friday, 14 February 2014 19:48:08 UTC