Renaming await Functions for Better Semantics
Problem
The current function names awaitAll() and awaitAllWithErrors() are misleading:
awaitAll() sounds like “wait for all,” but actually cancels all coroutines on the first error.
awaitAllWithErrors() has safer behavior but is hidden behind a longer name.
- It violates the principle of least surprise.
- Unsafe default behavior may lead to resource loss in production.
Goal
Make the API more intuitive and safe by default, renaming functions so that:
- Simple names provide safe (fail-safe) behavior.
- More complex names require an explicit choice of unsafe (fail-fast) behavior.
- Names accurately reflect the actual function behavior.
Tasks
1. Renaming in RFC Document
1.1 Change Function Definitions
File: base.rfc
Current names → New names: