Re: [heycam/webidl] Please prefix getter/setter/callback interface with legacy so it's clear they are (#100)

> some of the API goals of Typed OM as currently specified to be broken by design. Not the actual functionality, but the use of typing and typechecking. 

And note, of course, that this isn't a special goal of Typed OM, it's part and parcel of *literally all of WebIDL*. 

> I think there is general agreement that named getters/setters are a bad idea.
>
> For indexed getters/setters, things are complicated, not least because there are legitimate use cases that have no other solutions right now. Indexed setters do require some careful spec prose around out-of-bounds sets.

I strongly agree that named getters/setters should be considered legacy and/or given a name that clearly demonstrates they're special-use and should have thoro review of the necessity. Maps satisfy all their use-cases much better.

For indexed getters/setters, yeah, I'm finding there's a lot of missing guidance on how to do these right. :(

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/heycam/webidl/issues/100#issuecomment-366011068