-
-
Notifications
You must be signed in to change notification settings - Fork 64
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
change of no-error path behavior leading to maybe-uninitialized warning #264
Labels
Comments
I've seen this in the work code base as well, and I too would like it to go away. I'll hopefully create some time to do it soon. Thanks for the report. |
Possibly related, I've started to observe
It looks like clang-tidy cannot deduce that full log
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Repro and detailed description here:
https://godbolt.org/z/YG6e8q3Y5
Excerpt:
Very likely that this is a GCC issue (in fact, can't be reproduced in trunk). Yet, it is a curious phenomenon and causing production hassle with our boost upgrade. I am wondering if this is an expected change with later Outcome versions, or worse and crucially if the usage in the reproduction code is somewhat making incorrect assumptions.
Or, if there is confirmation this is just a silly GCC bug, it'd be a good enough resolution.
thanks
The text was updated successfully, but these errors were encountered: