pillaiindu
These two work:
iex(1)> for {key, val} <- %{"a" => 1, "b" => 2}, do: {key, val * val}
[{"a", 1}, {"b", 4}]
iex(2)> for {key, val} <- %{"a" => 1, "b" => 2}, into: %{}, do: {key, val * val}
%{"a" => 1, "b" => 4}
But this one gives syntax error:
iex(3)> for {key, val} <- %{"a" => 1, "b" => 2}, do: %{key, val * val}
** (SyntaxError) iex:3:62: syntax error before: '}'
|
3 | for {key, val} <- %{"a" => 1, "b" => 2}, do: %{key, val * val}
| ^
Why?
Why can’t we use map directly after the do: in list-comprehensions?
Trending in Questions
I having some trouble figuring out if I have set myself too strict of standards for my production server. Currently I can handle 75% of r...
New
Hello,
I’m trying to build a basic Phoenix web-app, and I’d like to use Tailwind.
However, when I launch mix phx.server, I get an error...
New
I’m working on a small exercise involving update_in/3, and I came up with this solution:
data = %{
name: "Periodic Table",
category:...
New
I’ve got trouble wrapping my head around the order in which functions are called in this snippet (from Phoenix’s authentication):
toke...
New
Is there any way to avoid the Hologram compiler running when using iex? It seems like the front-end code could potentially be disregarded...
New
** (ArgumentError) expected :max_attempts to be a positive integer, got: {:@, [line: 10, column: 19], [{:max_attempts, [line: 10, column:...
New
Hello folks!
So at work, we are seeing some situations where we have to define some “fixed” strings that are used across the codebase in...
New
Other Trending Topics
Edit: 2026 May 15 - This post is archived.
Mob is alive!!
Main docs: mob v0.7.11 — Documentation
A bit of explanation for the slightly c...
New
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
A little off-topic, but I feel like people here have a good head on their shoulders.
I used to be quite good at making software. Was luc...
New
Hey. Is there anyone here who creates agents in their apps? Not talking about using agents, but creating them. I’m finding it pretty diff...
New
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
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
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex











Showing Posts 1 to 8- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
Kurisu
I think you have a synthax error on the way you’re trying to define the map. It is not about the
forordo.One way you could achieve the map definition would be :
or
eksperimental
Exactly, the first one works because what he is defining is a tuple, not a map.
pillaiindu
Yes, it’s a tuple not a map, and not even a tuple, because tuple doesn’t have
%{.I did it accidentally and it took time to catch the mistake. I wanted to see if someone else can catch the mistake, because the error message doesn’t specifically point it out.
%{"#{isn’t even needed, usingkeydirectly works.for {key, val} <- %{"a" => 1, "b" => 2}, do: %{key => val * val}works.msimonborg
Your map syntax itself is invalid
Kurisu
Ah you’re right ! ^^
No string interpolation is necessary indeed.
I tought it won’t work for map with atom keys, but it also works as well:
03juan
It’s interesting that the first syntax error points to the end of the malformed map, but the second one to the correct place, at the comma. Perhaps a bug because of the for comprehension?
msimonborg
Due to the for comprehension, yes, but I would hesitate to label it a bug.
foris a macro, and the code is being received as quoted expressions. I’ve written macros but my knowledge is not very deep to understand error handling and introspection. The pointer seems to be pointing more generally to the offending expression, maybe because of how these details are implementedLostKobrakai
Maps are valid returns for
for, unlessinto: %{}is supplied as well. So it’s tricky.