-
Notifications
You must be signed in to change notification settings - Fork 751
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
[rand.req.seedeq], [rand.req.dist], [char.traits.require] Eliminate "compile-time" complexity #6839
base: main
Are you sure you want to change the base?
Conversation
@jwakely, @jensmaurer: I'm sympathetic to improving this, but can we do better than just deleting "compile-time"? Can we maybe say something along the lines of something being constant-evaluated? |
@tkoeppe, these are typedefs. There is no evaluation going on at all, not even constant evaluation. We should just merge this. |
Suggest to improve commit descriptions to say "... for typedefs" |
OK, makes sense. @Eisenwave Could you please update the commit messages? Also please just say "remove" instead of the overly lyrical "eliminate". |
I'm on vacation. If it's not urgent, I can do it in two weeks when I'm back. |
@Eisenwave Ping 🌴 |
ad0f50d
to
2bd2de7
Compare
Related to #5641.
In short, the C++ standard doesn't have a clearly-defined notion of "compile-time" or "run-time".
Instead of specifying that these type aliases have "compile-time complexity" (whatever that's supposed to mean) we can just leave the cell empty. No evaluation takes place here, so it's meaningless to talk about complexity.