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
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
Hi everyone.
My team and I have been working on a fairly modest app based around video streaming and chat, but we’ve landed a customer t...
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 really like the adapter patterns that ecto, nebulex, waffle, etc. use and would love find something similar for a key management servic...
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
How Can I Optimise Compile Time Dependencies
I have been building an elixir application for about 2 years now. Many modules and files ha...
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
Other Trending Topics
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
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
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
I love Elixir. It’s one of 2 programming languages I’ve ever fallen in love with.
But I don’t use it anymore.
Serverless was the promis...
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
- #ai
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #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.