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

US367 6-15 Instead of header inclusion, also permit header unit import #363

Closed
wg21bot opened this issue Oct 25, 2019 · 2 comments · Fixed by cplusplus/draft#3481
Closed
Labels
Projects
Milestone

Comments

@wg21bot
Copy link
Collaborator

wg21bot commented Oct 25, 2019

Requirements that a header be included before a language feature is functional should also allow for importing that header (unit), While we will file additional comments for the cases we identify, this is a catch-all comment to adopt the principle and similarly fix any places we miss.

Proposed change:
When a header be included before a language feature is functional should also allow for importing that header (unit).

@wg21bot wg21bot added the CWG Core label Oct 25, 2019
@jensmaurer jensmaurer added the modules Modules label Oct 26, 2019
@jensmaurer jensmaurer added this to Deferred for other group input in CWG Nov 5, 2019
@jensmaurer jensmaurer moved this from Deferred for other group input to TODO in CWG Nov 5, 2019
@jensmaurer jensmaurer moved this from TODO to Deferred for other group input in CWG Nov 5, 2019
@jensmaurer jensmaurer moved this from Deferred for other group input to Drafting in CWG Nov 5, 2019
@jensmaurer
Copy link
Member

CWG in Belfast: Tentatively accepted; drafting assigned.

@jensmaurer jensmaurer moved this from Drafting to Accepted in CWG Nov 5, 2019
@jensmaurer
Copy link
Member

CWG in Belfast: Accepted. See paper P1971R0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
CWG
Accepted
Development

Successfully merging a pull request may close this issue.

2 participants