- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Tue, 13 Sep 2016 15:23:39 +0200
- To: Boris Zbarsky <bzbarsky@mit.edu>
- Cc: Adam Bergkvist <adam.bergkvist@ericsson.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>
On Tue, Sep 13, 2016 at 3:12 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote: > Maybe the right answer is to really make range-enforcement a property of the > type, nix the [EnforceRange] thing entirely and just have an "enforced long" > type and similar for other numeric types.... That's what we ended up doing when we hit exactly this problem with ByteString/USVString (formerly [EnforceUTF16] DOMString or some such)... -- https://annevankesteren.nl/
Received on Tuesday, 13 September 2016 13:24:07 UTC