3 ms·
Yep, except that it is not there. There was quite a discussion about (&), (|>) and what not on the mailing list. No consensus… http://www.haskell.org/pipermai
by lelf 14y ago
Yep, except that it is not there.
There was quite a discussion about (&), (|>) and what not on the mailing list. No consensus…
http://www.haskell.org/pipermail/libraries/2012-November/018832.html http://www.haskell.org/pipermail/libraries/2012-November/018...
http://hackage.haskell.org/trac/ghc/ticket/7434 http://hackage.haskell.org/trac/ghc/ticket/7434
- nrlucas 14y agoF# obviously approves |>, but in my software project that has been continually maintained for ten years, we introduced -->. Now re-factoring our project we use |>. It kind of messes with my sight against pattern matching in OCaml though.
- gizmo686 14y agoBikesheddin at its finest. When I was first learning haskell, I thought I was missunderstanding how to use the language because I would define (|>) a f = f a in every project I do. I thought that such an operator seemed so obvious that it couldn't possibly not be standard. The fact that it wasn't seemed to suggest that I was doing Haskell badly, and that there was some deep reason I should only work right to left using operators such as ($), which I still do use a fair amount.