Re: [heycam/webidl] [wip] First pass at adding internal slots (#495)

I don't think IDL's type system should be different; it's a subset. When IDL says "USVString" that should convert a JavaScript string to a scalar value string (and vice versa when used for a return value). "ByteString" should convert a JavaScript string to a byte sequence (and a byte sequence to a JavaScript string for the return value).

I don't think it should be separate. I want the class/interface description to take care of these so it's clear they're allocated when the class/interface is (and IDL can say as much). Describing each object with two pieces of data would still allow for that, but it gets messier as you first have to do some kind of "find the other bits of data" step.

We should make it clear that implementations can have different strategies and use pointers to share slot data and such, but that's already the case for all algorithms. I don't think that takes away that specifications should strive for clarity and a single object description provides that.

-- 
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/pull/495#issuecomment-357430798