Re: [heycam/webidl] Describing overloaded methods (#241)

I believe the intent in IDL is in fact that you have different spec-defined algorithms (which can, of course invoke some common spec algorithm) for each overload.

The other option is to treat them as a single algorithm that gets invoked... but then that algorithm needs a way to tell which overload it was invoked as.  Which doesn't exist right now, really.  The 2d context algorithms speak of arguments being "not specified" but that's really not a thing...

Presumably specs do generally want to end up in some common algorithm after they do whatever processing they want to do on the arguments they were given that can't be expressed in IDL.  But that's most  clearly handled by doing that processing and then calling out to the common algorithm, I think.  In the specific case of the FormData method, for example, you would have only the Blob overload doing various stuff to produce a different value...

-- 
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/241#issuecomment-261343436