Sebb
I can do:
if true, do: :foo, else: :bar
and:
if true do
:foo
else
:bar
end
And I can do:
for i <- 0..3, do: {i, i+i}, into: %{}
but not:
for i <- 0..3 do
{i, i+i}
into
%{}
end
![]()
why is that?
Trending in Questions
Hi all,
I’m working on a Phoenix project where I need to make external HTTP requests and I’m trying to choose between Req and HTTPoison....
New
I’m very new to Elixir, so sorry if this is a silly question:
I am wondering what happens to the mailbox of a process when the machine i...
New
How do I tell Hologram not to escape HTML when substituting into templates?
{Textile.render(@product.long_description)}
escapes the HTM...
New
Background
When trying to execute mix release on a Windows 11 machine for a Phoenix project I get the following error:
* assembling mark...
New
I’d like to create a file with 600 permissions (rw-------), but there’s a race condition if I create it and then change the permissions. ...
New
Is there a way to import record definitions in the iex shell for pretty printing (similar to the rr command in the erl shell)? This woul...
New
When I use Mix.install with a git dependency, using git@github.com:... how do I change the SSH identity used?
I’ve got two Github accoun...
New
Other Trending Topics
Hey there,
I haven’t seen a list of useful Elixir specific skills for the popular AI tools yet so I’m starting one here with my first.
...
New
Hi everyone :waving_hand:
I wanted to share something I’ve been building — NowBlind, a random chat app designed to help people discover ...
New
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
(I just needed to vent somewhere and LinkedIn is full of hope, or hype, I’m not sure which exactly)
AI dream has many faces, but general...
New
Localize is the next generation localisation library for Elixir. Think of it as ex_cldr version 3.0. The first version will be released ...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
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
- #code-sync
- #discussion
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #elixirconf-us
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #elixirconf-eu
- #processes
- #security
- #api
- #forms
- #performance











Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
hauleth
Because
elsegot special treatment to ease user experience. This sugar is not available for any other atom outside the small set of predefined ones (else,rescue,catch, andafter).Sebb
So I can’t use
into,uniq,reducein afor ... endblock?josevalim
You can, you have to pass them before the do.
chungwong
and:
are different, although they look similar.
The first form is actually a
ifmacro accepting two arguments.And to make the second form works, we need a
intomacro which I don’t think we have it.hauleth
That is not true. Both are exactly the same thing for the compiler:
lud
Yes they are the same. A
doblock after a call adds the[do: ...]argument to the function/macro call on the left.So if you call this (notice the parentheses for the
ifcall)The compiler kind of rewrites it to
if(a == 1, [do: :ok])This works for functions too:
This will output the following:
But as
myfun/2is a function and not a macro, the block is evaluated before being passed to the function, hence you see[do: 3], whereas with macros the quoted block is passed. This syntactic sugar is then less useful for functions.The
formacro is special, because if you passinto: %{}, do: stuff(), thedoandintoare in the same keyword list ; if you passinto: %{}and then ado endblock, the compiler will add another argument to thefor()call, containing just thedoblock:I guess that is why
foris defined inKernel.SpecialFormsas an error because it is handled at the compiler level.hauleth
Well, no. It is still consistent behaviour among all other calls:
There are 2 reasons why
foris special form and not “regular” macro:<<a <- binary>>syntax need special handlingSo all of the above forces the Elixir to treat
foras a “special thing” within parser itself.lud
I don’t understand to what you say “no”.
I mean in your example it calls two different
foofunctions. Theforconstruct handles that in a special way, there are not several definitions forforto my knowledge in the Elixir code.hauleth
As I said, it is literally impossible to define
forin Elixir. I meant thatdo: 10anddo … endaren’t really treated differently just forfor, but the same rules applies to all calls.foris special form not because ofdobut because eachx <- yis separate argument, sofor i <- 1..10, do: iis 2-ary function andfor i <- 1..10, j <- 1..10, do: i + jis 3-ary function. So eitherforwould need to have N different heads and just fail in case if someone would like to use more than that, then it would fail (see older Rust compilers to see that problem, thereDebugis defined only up to 32-ary tuples, as there is no variadic generics). Due that problemforandwithmust be defined as special forms, because they require parser magic to be then expanded properly.lud
Ok so it is not defined as a special form just for the arity problem, but otherwise it is just what I said, basically it is a special form because it requires special treatment at the compiler level.