dry-python / dry-python/returns
Think about typed do-notation
Abierto
enhancement
help wanted
question
- Lenguaje dominante
- Python
- Estrellas
- 4.4k
- Forks
- 155
- Merge medio
- 2 h 27 min
- PR fusionados (30 d)
- 22
Descripción
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.
Guía de contribución
Evaluación
Este issue todavía no se ha evaluado.