JoshMcguigan / JoshMcguigan/multi_try
The most ergonomic solution!
- Dominant language
- Rust
- Stars
- 81
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
The most ergonomic solution!
Hello, Josh!) I personally see this small crate as one of the best ways (even after 5 years) to manage errors (accumulating them all). There are alternatives: frunk, semval, garde, rust2fun, valid.
But the first one, of course, is very functional, non-idiomatic, and relatively complex. The next two, on the contrary, have infrastructural limitations for large-scale uniform application.
I really like the last two crates too.
The value of your approach is in its simplicity, clarity, and the ability to build a more special solution if necessary. And without the need to dive deeply into applicative functors and other Haskel twists and turns (although this is also interesting).
Yes, Rust is not purely functional, so you have to add some magic to the impl_multi_try macro! - but its purpose is clear, even if you don’t have much experience writing macros. And this is your merit! Thank you =)
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue body is positive feedback and does not name a file, test, entry point, or requested change. Clarify the desired improvement and its acceptance criteria before investigating the crate or defining what done means.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100