Skip to content

[dcl.ambig.res]/1 Fixed ambiguity with resolving object and function declarations CWG2620 #2854

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

Closed
wants to merge 1 commit into from
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions source/declarations.tex
Original file line number Diff line number Diff line change
Expand Up @@ -2302,9 +2302,8 @@
In that context, the choice is between a function declaration with
a redundant set of parentheses around a parameter name and an object declaration
with a function-style cast as the initializer.
Just as for the ambiguities mentioned in~\ref{stmt.ambig},
the resolution is to consider any construct that could possibly
be a declaration a declaration.
The resolution is to consider any construct that could possibly
be a function declaration a function declaration.
\begin{note}
A declaration can be explicitly disambiguated by adding parentheses
around the argument.
Expand Down