Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[over.call] wording makes little sense #1642

Closed
brevzin opened this issue Jun 12, 2017 · 1 comment · Fixed by #3625
Closed

[over.call] wording makes little sense #1642

brevzin opened this issue Jun 12, 2017 · 1 comment · Fixed by #3625
Assignees

Comments

@brevzin
Copy link
Contributor

brevzin commented Jun 12, 2017

This is a purely editorial issue. The wording currently reads:

Thus, a call x(arg1,...) is interpreted as x.operator()(arg1, ...) for a class object x of type T if T​::​operator()(T1, T2, T3) exists and if the operator is selected as the best match function by the overload resolution mechanism ([over.match.best]).

What does it mean for T::operator()(T1, T2, T3) to exist? What are T1, T2, and T3? The idea here, I think, is to clarify that operator() is called if it exists, as opposed to some function pointer conversion that could happen and be a better match... I can't propose a better wording since I'm not entirely sure what the wording is currently intended to convey.

@jensmaurer jensmaurer added the decision-required A decision of the editorial group (or the Project Editor) is required. label Oct 3, 2019
@jensmaurer
Copy link
Member

Editorial meeting: Drop "Thus". Drop (T1,T2,T3). Instead of "args1...", use "expression-list/opt" (grammar). Move "A call" to a new paragraph. Also in 12.6.5 and 12.6.6. Use a fairly large hammer, possibly excising "x" as well.

@jensmaurer jensmaurer removed the decision-required A decision of the editorial group (or the Project Editor) is required. label Oct 21, 2019
@jensmaurer jensmaurer self-assigned this Jan 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants