Improve compiler diagnostics for when a sender & receiver won't connect
@ericniebler is already working on this.
Since Mar 16, 2023.
- #835 by @maikel — closed without merging
Assessment
This issue has not been assessed yet.
Description
I think stdexec can absolutely have good diagnostics, but we're a long way from that. I've done a bit of that with the receiver_of concept, which gives good diagnostics when it fails. (It tells you which completion signature the receiver lacks a handler for. See here.)
I'm thinking it should be possible to retrofit this sort of type-based error propagation into, say, get_completion_signatures and make_completion_signatures, so that users get a sensible diagnostic when a sender and receiver don't connect. And then change the routines like sync_wait to surface the error information when the requirements aren't satisfied.
- Dominant language
- C++
- Stars
- 2.4k
- Forks
- 270
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 37
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NVIDIA/stdexec
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 66/100
-
Difficulty 3/5 1-2 days Newbie friendliness 74/100
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
NVIDIA/cuda-samples#453 ·