Re: [heycam/webidl] [EnforceRange] should normatively specify RangeError (#359)

> especially the claim that EnforceRange is not testable or can throw any error. 
...
> which throws a TypeError.

When reading the spec and encountering ConvertToInt in the octet definition, I incorrectly assumed it would be semantically the same as `ToInteger` (which can only throw TypeError exception when ToNumber encounters a Symbol or ToPrimitive encounters an @@toPrimitive return value that's an object). Based on that incorrect assumption, it appeared that `[EnforceRange]` was under-specified, however it's clear now that it's just poorly specified—but specified nonetheless, and as such is not likely to be changed (I'm sure that doing so would break the web)


> Is this a change request to change it to RangeError?

The request would've been to specify that `[EnforceRange]` would throw a `RangeError`, because that's what RangeError is for, but I'm going to drop the issue in favor of the web.



-- 
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/359#issuecomment-300586637