I saw just
&
I don’t think this is correctly parsable, as it is hard-coded in the parser to be an arity-1 operator. I could be wrong. though. it would have to be :&
language enhancement
I don’t think it’s appropriate as a language enhancement. I’m not sure what a pipe extension should look like.
for starters, I want to to sometimes assign a value to the end of the pipe.
foo = bar
|> baz()
|> quux()
to:
bar
|> baz()
|> quux()
|> foo
This should obviously be a match operation, so:
{:ok, foo} = bar
|> baz()
|> quux()
becomes:
bar
|> baz()
|> quux()
|> {:ok, foo}
well that doesn’t feel right (and conflicts, for example, with the proposal in this thread), but probably there should be SOME operator that does this, and now it becomes a challenge to decide which one “deserves” to be on the end of |>. The best choice is to have |> do one thing and one thing well.
Anyways there are two similarly shaped operators: ~> and ~>>, so those are both options, if anything is going happen to change the language it would be to ask the elixir team to release more pipe-y operators, into the parser for people to use in their libraries, like ->> and =>>, if we want to get wild, ==>, =~>, =-> might be fun too.
