Skip to content

Conversation

@AlexGuteniev
Copy link
Contributor

Towards #1078. Follow-up of #2759.

Attempt to provide angrier message than for deprecation, in order to actually remove this emergent complexity someday.

Oops, and libc++ tests give deliberate coverage on that. Or is it more of oops that we don't?

@AlexGuteniev AlexGuteniev requested a review from a team as a code owner January 1, 2026 19:45
@github-project-automation github-project-automation bot moved this to Initial Review in STL Code Reviews Jan 1, 2026
@StephanTLavavej StephanTLavavej added the enhancement Something can be improved label Jan 3, 2026
Comment on lines +1329 to +1330
"The effect of instantiating the template std::complex for any type other than float, double, or long double "
"is unspecified. The possibility of such instantiation will be removed in a future version. "
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be better to say "a cv-unqualified floating-point type" (see [complex.numbers.general]/2) which looks more future-proof?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure. I copied that from the deprecation message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement Something can be improved

Projects

Status: Initial Review

Development

Successfully merging this pull request may close these issues.

3 participants