Re: [whatwg/webidl] Allow DOMException subclasses to be used as exceptions (PR #1211)

@bathos commented on this pull request.



>  
 *   <dfn exception>EvalError</dfn>
 *   <dfn exception>RangeError</dfn>
 *   <dfn exception>ReferenceError</dfn>
 *   <dfn exception>TypeError</dfn>
 *   <dfn exception>URIError</dfn>
 
-These correspond to all of the ECMAScript [=ECMAScript/error objects=]
-(apart from <l spec=ecmascript>{{SyntaxError}}</l> and {{Error}},
-which are deliberately omitted as they are reserved for use
-by the ECMAScript parser and by authors, respectively).
-The meaning of each [=simple exception=] matches
-its corresponding error object in the
-ECMAScript specification.
+These correspond to all of the ECMAScript [=ECMAScript/error objects=] (apart from
+<l spec=ecmascript>{{SyntaxError}}</l> and <l spec=ecmascript>{{Error}}</l>, which are deliberately

pre-existing, but: AggregateError, too.

(Given there’s at least [one more in the pipeline](https://arai-a.github.io/ecma262-compare/snapshot.html?pr=3000#sec-suppressederror-constructor), maybe keeping this in sync is too awkward and the gist could be conveyed without enumerating the excluded constructors...?)

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/webidl/pull/1211#pullrequestreview-1455165324
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/webidl/pull/1211/review/1455165324@github.com>