async_promise_type possibly unitialized value #154
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jbaldwin
force-pushed
the
issue-153/gcc13-possibly-uninitialized-value-warning
branch
7 times, most recently
from
e34fed2 to
3ffc4aa
Compare
The std::variant for callback or future/promise with gcc-13 seems to be triggering an uninitialized value warning. We can tell it isn't uninitialized but the compiler seems to be thinking the 2nd type in the variant, which is the callback type, is unitialized _when_ the promise type, 3rd type in the variant, is the one being initialized. Closes #153
jbaldwin
force-pushed
the
issue-153/gcc13-possibly-uninitialized-value-warning
branch
from
3ffc4aa to
d743b67
Compare
jbaldwin
deleted the
issue-153/gcc13-possibly-uninitialized-value-warning
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The std::variant for callback or future/promise with gcc-13 seems to be triggering an uninitialized value warning. We can tell it isn't uninitialized but the compiler seems to be thinking the 2nd type in the variant, which is the callback type, is unitialized when the promise type, 3rd type in the variant, is the one being initialized.
Closes #153