add textobject queries for beam languages, capture rust closures as functions

[the-mikedavis]

Adds textobject queries for Erlang, Elixir & Gleam

Also includes an update for tree-sitter-erlang that makes function_clause a named node.

Erlang and Elixir may have multiple function clauses for one function:

fib(0) -> 0;                                %% one textobj, ]f selects this line
fib(1) -> 1;                                %% this line is another
fib(N) when N > 0 -> fib(N-1) + fib(N-2).   %% and this line is another

In these queries I'm capturing function clauses as function.around but I'm curious if others think it should be around the entire function definition.

[pickfire]

Ah, I didn't realized textobjects is specifically used for this. Looks good to me although I didn't check closely.

[archseer]

In these queries I'm capturing function clauses as function.around but I'm curious if others think it should be around the entire function definition.

Since this is Elixir/Erlang-specific @connorlay, wdyt? 😀

I imagine the issue could be that clauses aren't always defined next to each other

[connorlay]

In these queries I'm capturing function clauses as function.around but I'm curious if others think it should be around the entire function definition.

Elixir supports multiple function heads like this:

def foo(:bar) do
  "bar"
end

def foo(:baz) do
  "baz"
end

...which I would consider two separate textobjects. However, if written as an anonymous function with multiple clauses like this:

foo = fn
  :bar -> "bar"
  :baz -> "baz"
end

I would consider that one textobject. Does that make sense @the-mikedavis @archseer ?

[the-mikedavis]

I added queries for anonymous functions as well, so:

fn
  :ok -> 1
  :error -> 2
end

]f/maf selects the whole anonymous function and mif selects the body of each clause, so 1 for the first clause and 2 for the second.

We could probably do the same for rust closures, eh?

[archseer]

We could probably do the same for rust closures, eh?

Yup!