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

Yeah I think the surface-level design of OAs is right, at least at first blush. There's just something wrong with the details of the guts, if something is preventing an OA from holding another OA. The details of the backing list and getting/setting from it should be tied to the OA object, not to the interface that happens to have an OA attribute. If nesting is illegal it implies that OAs can't live by themselves as, say, something that a method can return (in particular, it implies that you can't make an interface that extends from OA).

But I haven't dug into these details yet so I'm not sure what, if anything, is actually problematic, or if it's just something that needs a quick tweak to fix an accidental error in one of the algos.

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

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