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

fix residual suggestions that overload resolution might not always happen #3297

Closed
zygoloid opened this issue Oct 14, 2019 · 0 comments · Fixed by #3588
Closed

fix residual suggestions that overload resolution might not always happen #3297

zygoloid opened this issue Oct 14, 2019 · 0 comments · Fixed by #3588
Assignees
Labels
cwg Issue must be reviewed by CWG.

Comments

@zygoloid
Copy link
Member

CWG has moved wording changes to make overload resolution always happen, but there are some remaining cleanups. As proposed by CWG, we should assemble a pull request for these and run them past CWG before applying.

Specifically: [over.match.call] talks about only applying to "a set of overloaded functions" (also search for that phrase elsewhere), and [expr.call]p7 suggests we could have selected a function that lacks a default argument for a parameter (that can't happen after applying the wording of editorial issue #3235 as a core issue).

@zygoloid zygoloid added the cwg Issue must be reviewed by CWG. label Oct 14, 2019
@jensmaurer jensmaurer self-assigned this Dec 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cwg Issue must be reviewed by CWG.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants