Think about typed do-notation

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.

Comece lendo a discussão removida de @pipeline e a issue relacionada Failure-types #90; em seguida, compare os problemas listados com IOResult, FutureResult, Maybe e Result. A issue não especifica arquivos, testes nem um ponto de entrada para a implementação; o trabalho não estará completo até que o projeto concorde com um design concreto para do-notation tipada.