Skip to content

US 25-060 10.3p6 [module.import] Allow "static inline" names in header units #497

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
wg21bot opened this issue Oct 30, 2022 · 2 comments
Closed
Labels
Milestone

Comments

@wg21bot
Copy link
Collaborator

wg21bot commented Oct 30, 2022

After implementation and deployment of this rule and the paragraphs (6.3) referenced in the note, it turns out that functions defined “static inline” in headers (often shared between C and C++) are more common than realized and the restriction of not being them to refer such names/entities constitutes a huge practical usability problem

Proposed change:

Permit uses of names/entities defined as “static inline” in header units, and problem that each translation unit that odr-uses those names as a TU-local copy of those definitions, which corresponds to the behaviour if the header units had been #included.

@wg21bot wg21bot added the EWG Evolution label Oct 31, 2022
@jfbastien
Copy link
Collaborator

Duplicate: #427

@jensmaurer jensmaurer changed the title US 10.3p6 [module.import] Allow "static inline" names in header units US 25-060 10.3p6 [module.import] Allow "static inline" names in header units Nov 3, 2022
@jensmaurer jensmaurer transferred this issue from another repository Nov 3, 2022
@jensmaurer jensmaurer added this to the CD C++23 milestone Nov 3, 2022
@erichkeane
Copy link

No objection to unanimous consent that this is a duplicate as stated above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants