example suggestion: dealing with Tasks with different error types
Open
Nobody has claimed this yet.
example suggestion
- Dominant language
- Shell
- Stars
- 46
- Forks
- 19
- Avg merge
- 13h 38m
- Merged PRs (30d)
- 19
Description
Task.await is easy to reach for but its type signature makes it look like all tasks involved need to have the same error type. In reality errors are automatically combined with open tag unions. This situation is worth an example because I imagine this could be a common question.
Contributor guide
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.
Research direction
Review the repository's existing examples and the entry point for Task.await, then read the relevant open tag union guidance. Add a focused example showing tasks with different error types being combined, and verify that it clearly demonstrates the behavior described in the issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- Half a day
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100