Re: [heycam/webidl] Possible mistake in overload resolution algorithm (#1009)

An abstraction over “iterator getting ... and using” might make sense, yeah, though it doesn’t seem like it would fit neatly into the three+ places it’s needed in slightly different ways. I think though that this specific case can be repaired without that, for example by introducing a second var for retaining a reference to the specific type which met the criteria in step 12.9 or perhaps by asserting in 14 that T is or includes (as inner type, member type, ...) exactly one sequence-like type (this is assured) and that that is the type being “used” rather that T (if they are not one and the same).

-- 
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/1009#issuecomment-897239540