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

[support.c.headers.other] Ambiguity in the requirements for includes #6075

Closed
8ightfold opened this issue Feb 9, 2023 · 3 comments
Closed

Comments

@8ightfold
Copy link

In [support.c.headers.other], it states that the <name.h> headers behave "as if each name placed in the standard library namespace by the corresponding header is placed within the global namespace scope". There are exceptions for several different parts of the headers, but it's left unclear as to whether or not including them in their corresponding <name.h> is optional.

Is it optional to for things such as std::byte to be included in the corresponding .h, or are they required but not put in the global namespace? The note makes it seem as if it's the former, but it's still currently ambiguous.

@tkoeppe
Copy link
Contributor

tkoeppe commented Feb 9, 2023

I'm not sure I understand the question, but whether <stddef.h> defines std::byte is unspecified, whereas it is guaranteed that ::byte is not defined by that header.

@8ightfold
Copy link
Author

That's what we wanted clarification on. As of now, it's not obvious that this is the case.

@8ightfold
Copy link
Author

I also just found out this isn't the place to submit issues like this. Thanks for your response.

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

No branches or pull requests

2 participants