refactor(example): make channel splitting structural rather than nominal - #376
Merged
Merged
Conversation
Key the awaitable-sender's error_code splitting on shape instead of the io_result name, per P4093: any tuple-like whose element 0 is error_code is an outcome. Single-element outcomes split across the value/error channels; compound ones (error_code plus payload) are rejected at compile time regardless of type name, since exclusive completion channels cannot carry a partial success without dropping data. Replace the io_result arity trait with tuple-protocol probes and update the shape coverage in the static assertions.
|
An automated preview of the documentation is available at https://376.capy.prtest3.cppalliance.org/index.html If more commits are pushed to the pull request, the docs will rebuild at the same URL. 2026-08-04 13:42:09 UTC |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #376 +/- ##
========================================
Coverage 98.09% 98.09%
========================================
Files 132 132
Lines 6288 6288
========================================
Hits 6168 6168
Misses 120 120
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
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.
Key the awaitable-sender's error_code splitting on shape instead of the io_result name, per P4093: any tuple-like whose element 0 is error_code is an outcome. Single-element outcomes split across the value/error channels; compound ones (error_code plus payload) are rejected at compile time regardless of type name, since exclusive completion channels cannot carry a partial success without dropping data. Replace the io_result arity trait with tuple-protocol probes and update the shape coverage in the static assertions.