Skip to content

Commit

Permalink
Correct non-normative summary of the overload resolution algorithm. (#…
Browse files Browse the repository at this point in the history
  • Loading branch information
Ms2ger authored and bzbarsky committed Nov 13, 2019
1 parent 5e51b73 commit 513c5ea
Showing 1 changed file with 8 additions and 4 deletions.
12 changes: 8 additions & 4 deletions index.bs
Expand Up @@ -11088,10 +11088,14 @@ Note: The HTML Standard defines how a security check is performed. [[!HTML]]
and there is an overload with an optional argument at this position, then
we will choose that overload. If there is no valid overload for the type of
value passed in here, then we throw a {{ECMAScript/TypeError}}.
The inspection of the value at the distinguishing argument index does not have any side effects;
the only side effects that come from running the overload resolution
algorithm are those that come from converting the ECMAScript values
to IDL values.
Generally, the inspection of the value at the distinguishing argument index does not have any
side effects, and the only side effects in the overload resolution algorithm are the result of
converting the ECMAScript values to IDL values.
(An exception exists when one of the overloads has a [=sequence type=] or [=frozen array type=]
at the distinguishing argument index.
In this case, we attempt to get the {{@@iterator}} property to determine the appropriate
overload, and perform the conversion of the distinguishing argument separately before continuing
with the next step.)

At this point, we have determined which overload to use. We now
convert the remaining arguments, from the distinguishing argument onwards,
Expand Down

0 comments on commit 513c5ea

Please sign in to comment.