|
496 | 496 | functions to be resolved against the same argument list.
|
497 | 497 | So that argument and parameter lists are comparable within this
|
498 | 498 | heterogeneous set, a member function is considered to have an
|
499 |
| -extra parameter, called the |
| 499 | +extra first parameter, called the |
500 | 500 | \defn{implicit object parameter},
|
501 | 501 | which represents the object for which the member function has been
|
502 | 502 | called.
|
|
508 | 508 | Similarly, when appropriate, the context can construct an
|
509 | 509 | argument list that contains an
|
510 | 510 | \defn{implied object argument}
|
511 |
| -to denote |
| 511 | +as the first argument in the list to denote |
512 | 512 | the object to be operated on.
|
513 |
| -Since arguments and parameters are |
514 |
| -associated by position within their respective lists, the |
515 |
| -convention is that the implicit object parameter, if present, is |
516 |
| -always the first parameter and the implied object argument, if |
517 |
| -present, is always the first argument. |
518 | 513 |
|
519 | 514 | \pnum
|
520 | 515 | For non-static member functions, the type of the implicit object
|
|
1076 | 1071 | \end{itemize}
|
1077 | 1072 | where in each case \tcode{operator<=>} candidates
|
1078 | 1073 | are not considered for the recursive lookup of operator \tcode{@}.
|
| 1074 | +\begin{note} |
| 1075 | +A candidate synthesized from a member candidate has its implicit |
| 1076 | +object parameter as the second parameter, thus implicit conversions |
| 1077 | +are considered for the first, but not for the second, parameter. |
| 1078 | +\end{note} |
1079 | 1079 |
|
1080 | 1080 | \pnum
|
1081 | 1081 | The argument list contains all of the
|
|
0 commit comments