-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Properly catch exceptions in {i|o}stream #2033
Conversation
Co-authored-by: Igor Zhukov <fsb4000@yandex.ru>
Co-authored-by: Adam Bucior <35536269+AdamBucior@users.noreply.github.com>
785036a
to
201c4cf
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are more suggestions than required changes, so I'll go ahead and approve.
From my point of view the current iostream situation is a bit broken. We do a lot of gymnastics to not call I think we could even get around the double exception it if we would simply call That said, I would definitely not touch this in this PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, I'll go ahead and push changes for one last round of feedback.
This comment has been minimized.
This comment has been minimized.
I'm mirroring this to an MSVC-internal PR - please notify me if any further changes are pushed. |
Thanks for fixing these EH bugs! 🐞 🦋 🎉 |
Fixes #1858