You could also try this if you don’t like the full fn syntax:
|> (&("\tKeywords = { " <> &1)).()
|> (&(&1 <> " }")).()
wmnnd
0
ghoetker
@CptnKirk @blatyo There is a package on Hex, PipeTo, that appears to offer much of this functionality. Adds a new pipe ~> with a placeholder _, leading to functionality like the following example
1 ~> Enum.at(1..3, _) # yields 2
The |> pipe continues to function as normal. In fact, if no placeholder is used, ~> performs just like |>. So, one could, I suppose, use ~> exclusively.
Haven’t played with it at all. Until I get my feet fully under me, I’ll err on the side of the basics, but you might find it worth looking into. Thanks for all your help.
@CptnKirk Interesting difference in philosophies. Perhaps because of my limited skills, I generally follow the quote attributed to Jamie Zawinski: “Some people, when confronted with a problem, think ‘I know, I’ll use regular expressions.’ Now they have two problems.”
1