3 ms·
maybe I'm being overly pedantic, but people seem to be confused about this: the pipes in your typical functional language (`|>`) is not a form of function comp
by sideeffffect 8y ago
maybe I'm being overly pedantic, but people seem to be confused about this:
the pipes in your typical functional language (`|>`) is not a form of function composition, like
```
f >> g === x -> g(f(x))
```
but function application, like
```
f x |> g === g(f(x))
x |> f |> g // also works, has the same meaning
f |> g // just doesn't work, sorry :(
```
- chriswarbo 8y ago> the pipes in your typical functional language (`|>`) is not a form of function composition What is a "typical functional language" in this case? I don't think I've come across this `|>` notation, or anything explicitly referred to as a "pipe", in the functional languages I tend to use (Haskell, Scheme, StandardML, Idris, Coq, Agda, ...); other than the Haskell "pipes" library, which I think is more elaborate than what you're talking about.