kerryb
I have some AST rewriting code (using Sourceror) that has started failing in Elixir 1.18 – I believe because unquote has become stricter about valid AST, whereas in earlier versions it was only an issue within macros.
The issue is that it’s trying to generate code containing a ~D[...] sigil. It works in Elixir 1.17:
iex(1)> quote do: unquote(~D[2025-01-07])
~D[2025-01-07]
But not in 1.18:
iex(1)> quote do: unquote(~D[2025-01-07])
** (ArgumentError) tried to unquote invalid AST: ~D[2025-01-07]
Did you forget to escape term using Macro.escape/1?
(elixir 1.18.1) src/elixir_quote.erl:542: :elixir_quote.argument_error/1
iex:1: (file)
I can use Macro.escape as suggested, but this inserts the date as a raw map instead of a sigil. This works, but doesn’t look great in the generated code:
iex(2)> quote do: unquote(Macro.escape(~D[2025-01-07]))
{:%{}, [],
[__struct__: Date, calendar: Calendar.ISO, day: 7, month: 1, year: 2025]}
Is there some way to end up with a call to the ~D macro in the generated code, rather than the resulting struct/map?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Master modern tools, write cleaner code, and tackle real-world challenges with Manning books, videos, and courses. Start building today.
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
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #ecto-query
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #hex
Our Sponsors
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.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Producing high quality Elixir screencasts since 2017.
The deployment platform built for Elixir: PaaS ease, VPS control.
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)
LostKobrakai
The quote/unquote has nothing to do with how the final generated code looks like. They’re just means of generating AST/injecting given AST in the resulting AST. You’d need to figure out the correct AST you want to return for sourceror:
Depending on what input you actually have you can build that AST for the return value.
This here is basically a noop. It does/did nothing.
kerryb
Thanks, that makes sense.
Yeah, in the real code there was a lot more stuff in the
quote.