Re: [heycam/webidl] Conversion to sequence<T> need not throw on a RegExp object (#145)

The historical context is twofold:

1. The intent was to make `Date` and `RegExp` distinguishable from dictionaries and sequences during overload resolution.
2. At one point the intent was that adding an overload should generally not change which overload got invoked for previously-accepted values.  That meant that an overload accepting dictionary or sequence should not accept `RegExp` or `Date`.  The idea was to avoid forward-compat bugs in APIs where behavior would change for existing callers when a new overload was added.

I think we've already deviated that principle in item 2 when we made dictionary and sequence distinguishable while still allowing iterables to represent dictionaries.  And I, personally, don't think it's a big deal to drop that principle entirely.

That said, for the specific case of `RegExp`, I think removing it entirely as https://github.com/heycam/webidl/issues/148 suggests is the right way to go.

-- 
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/145#issuecomment-241451186