Fix concept sender_in - #310
Open
Cra3z wants to merge 1 commit into
Open
Conversation
|
coverage: 93.454%. remained the same — Cra3z:main into bemanproject:main |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fix the implementation of
sender_in.The current implementation of
is_constantcan lead to incorrect results forsender_in. For example, letsndrbedecltype(ex::read_env(ex::get_allocator))，ex::sender_in<sndr, ex::env<>>should evaluate to false, but it evaluates to true on GCC. This issue appears to be caused byis_constantalways evaluating to true. See https://godbolt.org/z/71Ez1zKxv