Re: [whatwg/webidl] ObservableArray types in namespace (#1000)

I'm looking into copying some of the spec text for OAs for use in maplike/setlike (to solve #254) and ran into this question - OAs are excluded from a bunch of places that maplike/setlike interfaces are *not*, and it would be *really awkward* to add the restriction, but it's *really strange* to have them be treated differently.

I'm thinking this issue was resolved the wrong way around - it was originally raised just because the OA text was contradictory due to being overly specific in one part, and it got resolved by applying the more-specific condition everywhere. An OA is just... a Proxy object, tho. There's nothing about it that should actually make its use in any of these places problematic.

Would y'all mind if I PR'd to reverse this and do it the other way around instead, allowing OAs in all the places any other interface object is allowed?

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

Message ID: <whatwg/webidl/issues/1000/1113602109@github.com>