dry-python / dry-python/returns
Think about typed do-notation
Ouverte
enhancement
help wanted
question
- Langage dominant
- Python
- Étoiles
- 4.4k
- Forks
- 155
- Merge moyen
- 2 h 27 min
- PR mergées (30 j)
- 22
Description
I have removed `@pipeline` in `0.14` release.
It had lots of problems:
1. It was not working properly with `Failure` types: #90
2. It had problems with unwrapping complex values like `IOResult` and `FutureResult`
3. It had problems unwrapping containers of different types (you were not allowed to unwrap both `Maybe` and `Result` in the same `@pipeline`
4. It was encouraging imperative code in a functional codebase
I would love to have some solution instead! But, no ideas about how it should work or look like. So, any ideas are welcome.
Guide de contribution
Ouvrir le guide de contribution
Évaluation
Cette issue n'a pas encore été évaluée.