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’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
Hello,
I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
Other Trending Topics
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
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
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
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
- #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










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.