- Notifications
You must be signed in to change notification settings - Fork1.6k
Implement P3223R2 Makingistream::ignore() Less Surprising#5604
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
std::istream::ignore Less Surprisingstd::istream::ignore() Less Surprisingstd::istream::ignore() Less Surprisingistream::ignore() Less SurprisingZingam commentedJul 7, 2025
@frederick-vs-ja (This is not a review. Just a couple of questions.) Was the paper voted in as DR? I guess not. My reading of the Standard is that resolving the ambiguity is not required is that so? |
frederick-vs-ja commentedJul 8, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
I guess not, either. But according to thepaper issue I think it should be treated as a DR.
Yes. In this PR the ambiguity is resolved "by accident", which is a consequence of backporting. I don't think the ambiguity resolution is disallowed, either. |
StephanTLavavej commentedAug 7, 2025
I'm mirroring this to the MSVC-internal repo - please notify me if any further changes are pushed. |
fae8c55 intomicrosoft:mainUh oh!
There was an error while loading.Please reload this page.
StephanTLavavej commentedAug 8, 2025
🐱 😸 🐈 |
Uh oh!
There was an error while loading.Please reload this page.
As a Defect Report against old standard modes.Fixes#5618.
As a result of DR-backingP3223R2, the new overload is templated, and thus this PR happens to "constrain the new overload to prevent ambiguities" and keeps
in.ignore(100, -1L)well-formed.