- From: Anne van Kesteren <notifications@github.com>
- Date: Mon, 31 Jul 2017 07:26:33 +0000 (UTC)
- To: heycam/webidl <webidl@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <heycam/webidl/pull/392/review/53142992@github.com>
annevk commented on this pull request. > -The elements of an effective overload set are tuples of the form -<|callable|, |type list|, |optionality list|>. If the effective overload -set is for regular operations, static operations or legacy callers, then |callable| is an operation; -if it is for constructors or named constructors, then |callable| is an -extended attribute; and if it is for callback functions, then |callable| -is the callback function itself. In all cases, |type list| is a list -of IDL types, and |optionality list| is a list of three possible <dfn id="dfn-optionality-value" export>optionality values</dfn> – -“required”, “optional” or “variadic” – indicating whether -the argument at a given index was declared as being [=optional argument|optional=] -or corresponds to a [=variadic=] argument. -Each tuple represents an allowable invocation of the operation, +The [=set/items=] of an [=effective overload set=] are [=tuples=] of the form +([=effective overload set tuple/callable=], [=type list=], [=optionality list=]) +whose [=tuple/items=] are described below: + +* The <dfn for="effective overload set tuple" export>callable</dfn> is an operation I think the former is what I normally end up doing. (Not sure why though.) -- 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/pull/392#discussion_r130286499
Received on Monday, 31 July 2017 07:27:00 UTC