Re: [heycam/webidl] No seemingly consistent Shepherd story (#240)

It's certainly not something you should do, but as far as I can tell there's nothing that prevents it. We don't define operations for manipulating sequences and records and such that ensure these things.

We typically do this kind of thing by convention. E.g., we have "ASCII string" for a string where we guarantee to not put anything in that is outside the range U+0000 to U+007F. You can implement that as a typed thing, but the specification doesn't really. It just says it's an ASCII string and treats it like a string for all intents and purposes.

> Anne, what you're proposing would be a complete overhaul of Web IDL, which has a strong foundation in type theory right now and relies on the guarantees it provides during all of its algorithms, not just at the boundary.

There's nothing that would observably change, as far as I can tell. And we'd end up with less concepts and more reusable operations.

-- 
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/240#issuecomment-262278571