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
Hey guys,
I’ve got a huge CSV ( around 10 GB ) that needs to be processed hourly
Do you guys have any suggestions what is the best prac...
New
Hello!
Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app.
I creat...
New
I have what I’ve heard referred to as a “lookup table” in my database. This is a way of assigning codes to common values. One common lo...
New
What approach to take when sending live updates to “random” users Hi! I have a question, I have a little chat app, and when I create a DM...
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
Anyone here using Honeybadger?
My Honeybadger account is being overwhelmed with noise from some bots. Seeing a lot of
Bandit.HTTPError...
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
Other Trending Topics
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
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
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
There are three potential reasons for members of this forum to have a look at https://vutuv.de
You are tired or annoyed of LinkedIn.
Yo...
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
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixir-ls
- #elixirconf-us
- #ai
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
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.