Skip to content

Accidentally freestanding <exception> #7847

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
leni536 opened this issue Apr 22, 2025 · 2 comments
Closed

Accidentally freestanding <exception> #7847

leni536 opened this issue Apr 22, 2025 · 2 comments

Comments

@leni536
Copy link

leni536 commented Apr 22, 2025

// all freestanding

This line was added in #5713, when applying the changes proposed in P1642R11.

The paper does not propose this change. There is no corresponding wording in [compliance] either.

@leni536 leni536 changed the title Accidentally freestanding <exceptions> Accidentally freestanding <exception> Apr 22, 2025
@ben-craig
Copy link

The quoted line was proposed in the paper.

Instructions to the editor:
Please insert a // all freestanding comment at the beginning of the following synopses. These headers are entirely freestanding.

This change was rewording the status-quo. The <exception> header has been freestanding since C++98. The table in compliance already mentions the <exception> header.

Recommend closing as "not a bug" or whatever the equivalent is.

@leni536
Copy link
Author

leni536 commented Apr 22, 2025

Sorry, I can't read.

However I believe make_exception_ptr especially together with the upcoming P2927 can't possibly be freestanding, can it? But that's not an editorial issue.

@leni536 leni536 closed this as completed Apr 22, 2025
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