Re: [heycam/webidl] `maplike<>` requires spec authors to interact with a real-deal ES Map object (and others), with unfortunate consequences/complexity (#522)

Upon reflection, I think `maplike<>` works just fine for what it's intended to do - reflect something that's just like a `Map`. `Map`s store arbitrary JS values already, so it's fine to have an intervening "real Map" in there - the values come from the outside world anyway (or are explicitly constructed by the spec to be real JS objects).

I want to be doing something different, and storing a list of values for each key; I don't want the list to be a "real Array", because that's a lot of unnecessary complexity; instead, I want it to be the same as how `sequence<>` return types are handled, where they can be backed by an Infra list and turn into an Array when they cross the boundary.

It might still be better for `maplike<>` to be defined in terms of Infra objects, but it's a lesser concern now. I'll go ahead and close this, and re-open it if I have some more particular concern in the future.

-- 
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/522#issuecomment-367536276