sihui_io
rest is [“a”] and last_gift is “b”.
rest |> Enum.join(", “) returns “a”, which is a string.
“a” |> “#{}, and #{last_gift}” returns “a, and b”.
But when I pipe them together, I get ArgumentError.
rest |> Enum.join(”, ") |> “#{}, and #{last_gift}”
** (ArgumentError) argument error
What do I miss? ![]()
Trending in Questions
Hello!
Suppose you are building workflow (order / task / payment) processing system with the following requirements:
Each workflow con...
New
I’m in search of an Elixir library that offers PDF generation capabilities similar to Ruby’s Prawn. While there have been discussions abo...
New
I’m looking to build a personal workflow to quickly deploy web applications written in elixir/phoenix, for local consumption (ie not on t...
New
Before I dive in myself, did anyone successfully sprinkle Hologram into their existing LiveView app?
Looking for hints regarding:
Addi...
New
Hi all, I wanted to ask how the community is dealing with post-release steps.
Today we have Ecto migrations, which make sure that the db...
New
Kia ora,
We have been using elixir-google-api to connect to Google Drive. However, with the updates to Tesla due to CVEs this is now bro...
New
Hello,
I have an Elixir backend that implements a custom protocol over TCP. I want to load test the backend and assess the performance o...
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
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New
There has been a thread to discuss the Stack Overflow Developer Survey on this forum every year since 2018, so here’s yet another one for...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex










First 10 of 12 Posts
kokolegorille
You cannot pipe a variable into a string.
But You can
My guess is a string is not a function, and does accept only “” to be piped, but You can interpolate without pipe with “#{x}, and #{last}”.
sihui_io
Ha! That’s spot on! Thanks!
sihui_io
It turns out
a |> "#{}"doesn’t mean we are actually interpolating a into the position of#{}kokolegorille
It does not mean it’s piping a string into a string either…
sihui_io
ah, yeah…
doesn’t seem to be an intended behavior, then…
I wonder if it’s actually a bug now…
kokolegorille
Underneath, it’s
voltone
Right, so
"234#{five}"is actually<<"234", five::binary>>, which is invokingKernel.SpecialForms.<<>>. Piping something into that prepends the value at the front of that binary, if it is a legal parameter to<<>>.So in the end
"1" |> "234#{five}"expands to<<"1", "234", five::binary>>which happens to be legal. I don’t think it’s intentional.sihui_io
Didn’t know about
quoteuntil now. Seems super useful, thanks!That explains the ArgumentError:
Basically
#{}expects an argument to be passed in, but we are not passing anything to#{}when we dox |> "bb#{}". But"bb#{x}"does.sihui_io
That makes sense now, thanks!
adworse
You actually kind of may pipe a variable into the string interpolation if it’s wrapped into the anonymous function call, like
"test" |> (&"shmest #{&1}").()Looks ugly though.