I’ve always felt conflicted about the syntactic sugar that allows dropping brackets on keyword lists if they’re the final parameter of a function call. For instance, try explaining to a newcomer to Elixir why this should happen:
IO.inspect("bar", label: "foo")
# foo: "bar"
# "bar"
IO.inspect(a: "bar", label: "foo")
# [a: "bar", label: "foo"]
# [a: "bar", label: "foo"]
This bit of sugar makes reading code more confusing for a somewhat cool (but not essential, as far as I know), feature. If it were up to me, I would enforce brackets around keyword lists (and continue to push replacing keyword lists with map). So the previous calls would unambiguously be:
IO.inspect("bar", [label: "foo"])
IO.inspect([a: "bar", label: "foo"])
In any case, I lean more towards the side of keeping the syntax between function calls with and without parens as close as possible, and don’t think trailing commas inside function calls with parens moves the language in a good direction.
