-
Notifications
You must be signed in to change notification settings - Fork 771
[module.interface] Example does not seem to match normative wording CWG2491 #4540
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
Labels
cwg
Issue must be reviewed by CWG.
not-editorial
Issue is not deemed editorial; the editorial issue is kept open for tracking.
Comments
I don't have much special to add here; neither the minutes (from June 8) nor my contemporaneous notes say anything about the change. I suppose it might have had to do with typedef names for linkage purposes: typedef struct {} X;
export typedef X X; |
Editorial meeting 2021-04-16: Forward to CWG. |
I've requested that a core issue be opened for this. |
Was a core issue ever opened here? |
CWG2491, which struck "or typedef-name". |
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.
not-editorial
Issue is not deemed editorial; the editorial issue is kept open for tracking.
[module.interface]/6:
In the example,
export typedef S S;
redeclares a typedef-name whose preceding declaration was not exported. The normative wording seems to say that it's not OK, but the example says it is.I guess the example needs to be updated.
The "or typedef-name" part of the normative wording was added by P1787R6.
cc @opensdh
The text was updated successfully, but these errors were encountered: