Repository navigation
mention the parallel scheduler backend under the README example - #2349
Merged
ericniebler merged 1 commit intoOct 25, 2026
Merged
Conversation
ericniebler
approved these changes
Oct 23, 2026
Collaborator
|
/ok to test 6f42a29 |
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
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.
Looks like this is the segfault in #2128. Build the README example the way the install section says (link
STDEXEC::stdexec, or just-Ithe include dir) and nothing compiles in the parallel scheduler's backend, so on GCC 15/ Linux (all I tried) it links fine and then crashes on the first line ofmain.The godbolt link passes
-DSTDEXEC_PARALLEL_SCHEDULER_HEADER_ONLY=1, which is why it works there.hello_world.cppis the same code and gets the define or the compiled lib fromexamples/CMakeLists.txt, so the new line under the example names those same two options.