kwhite
I just ran into this unexpected behavior. I had a short function that is piping its result into other functions. When I converted the short function to a one-liner, the result changed.
I expected the EOL to terminate the if/do/else and not for the else only to be piped to the next line. (If you add parentheses around the if/do/else line, it works the same as the multi-line function.)
What terminates a one-line function? Where else might this happen?
defmodule F do
def fn1() do
if true do
1
else
0
end
|> Kernel.+(10)
end
def fn2() do
if true, do: 1, else: 0
|> Kernel.+(10)
end
end
F.fn1() # returns 11
F.fn2() # returns 1
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Elixir, Erlang & messaging conferences from Code Sync. Next up: ElixirConf US (10–11 Sep) & Code BEAM Europe (21–22 Oct), Haarlem + online.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #hex
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
zachdaniel
|>is an operator, just like+(although with lower precedence). This guide has some relevant info: Operators — Elixir v1.15.8If you consider this example:
+is left associative, so it goes “leftwards” until itgets to the end of its scopehas a complete expression for its left side. To visualize the “end of its scope” bit, you can remove the syntactic sugar given by keyword lists.It ends up being equivalent to something like this.
EOL in Elixir aren’t semantic. I feel like there might be a counter example to this? Not sure. I know spaces matter in some cases, i.e
%{foo:10}is not valid. I can’t come up with one off the top of my head.So with that in mind you can, your original syntax is parsed like so:
and so on.
EDIT:
thought of an example. newlines are relevant in multiline strings, i.e
The first
"""has to have an EOL immediately after it, and the last one has to have an EOL immediately before it IIRCkokolegorille
It’s important to use () when using functions in pipes
You could do it like this too