From 80aa72c60ecd0ac605041d22df2ea6a66178c5be Mon Sep 17 00:00:00 2001 From: timofey Date: Mon, 22 May 2023 10:11:37 +0000 Subject: [PATCH] `ApplicativeSelect` --- src/ch04/s05-fail.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/ch04/s05-fail.md b/src/ch04/s05-fail.md index b921e44..0a46398 100644 --- a/src/ch04/s05-fail.md +++ b/src/ch04/s05-fail.md @@ -9,4 +9,5 @@ ## ~~Lack of support for strict ordering of errors~~ * ~~Current (possible) implementations of having one error or another either allow short-circuiting on only one of them, or give them both the same priority. **Right now this model is considered the main one**, i.e. this restriction may get stabilised and standardised at some point.~~ * ~~More complex behaviours are expected to require a more complex execution model, with states taking messages from other states and optionally dropping their own execution, if their result\['s error\] is guaranteed to be "less severe" than the error it receives.~~ -* Solution: `Fallible::W::F::A>` +* Solution: `Fallible::W::F::A>`. +* Another solution: native select-based approach, `ApplicativeSelect`.