Thanks for the feedback!
True, I think that’s pretty strange too, but it’s still the most succint way I’ve found support this kind of matches with a sigil. For very good reasons, the sigil can’t influence what’s outside the sigil! This means that all “magic” syntax must happen inside the sigil.
Ideally, it should be something like this:
~k[a, b, c, d] = opts
but I don’t think I can make this work with Elixir’s macro system. I could use one of the undefined operators for something like this:
~k[a, b, c, d] <~ opts
What do you think?
Ok, maybe a match is not the right word for this. The goal of these keyword “matches” is actually to extract variables from keyword lists. I’ll think of a better name/better syntax
You’re probably right. This library kinda grew up “organically”, in that I started with something very simple based on regexes (actually not even regexes, I just used String.split()) and then I started adding to it. But I should look into implementing it with Code.string_to_quoted!/1.
