dry-python / dry-python/returns
Think about typed do-notation
オープン
enhancement
help wanted
question
- 主要言語
- Python
- スター
- 4.4k
- フォーク
- 155
- 平均マージ
- 2時間 27分
- マージ済み PR（30日）
- 22
説明
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.
コントリビューションガイド
評価
この issue はまだ評価されていません。