|
497 | 497 | functions to be resolved against the same argument list.
|
498 | 498 | So that argument and parameter lists are comparable within this
|
499 | 499 | heterogeneous set, a member function is considered to have an
|
500 |
| -extra parameter, called the |
| 500 | +extra first parameter, called the |
501 | 501 | \defn{implicit object parameter},
|
502 | 502 | which represents the object for which the member function has been
|
503 | 503 | called.
|
|
509 | 509 | Similarly, when appropriate, the context can construct an
|
510 | 510 | argument list that contains an
|
511 | 511 | \defn{implied object argument}
|
512 |
| -to denote |
| 512 | +as the first argument in the list to denote |
513 | 513 | the object to be operated on.
|
514 |
| -Since arguments and parameters are |
515 |
| -associated by position within their respective lists, the |
516 |
| -convention is that the implicit object parameter, if present, is |
517 |
| -always the first parameter and the implied object argument, if |
518 |
| -present, is always the first argument. |
519 | 514 |
|
520 | 515 | \pnum
|
521 | 516 | For non-static member functions, the type of the implicit object
|
|
1089 | 1084 | synthesized \tcode{operator<=>} candidates
|
1090 | 1085 | are not considered for the recursive lookups.
|
1091 | 1086 | \end{itemize}
|
| 1087 | +\begin{note} |
| 1088 | +A candidate synthesized from a member candidate has its implicit |
| 1089 | +object parameter as the second parameter, thus implicit conversions |
| 1090 | +are considered for the first, but not for the second, parameter. |
| 1091 | +\end{note} |
1092 | 1092 |
|
1093 | 1093 | \pnum
|
1094 | 1094 | The argument list contains all of the
|
|
0 commit comments