Match Inside Function (Rust-analyzer) selects function brackets

[abrassel]

Summary

When I hit "mif", I expect the body of the function, but not it's enclosing brackets to be selected.
Instead, everything other than the function definition gets picked.

This is repro'd on a recent Helix build, with rust-analyzer.

Reproduction Steps

I tried this:

fn part_1(maze: &Maze) -> usize {
    let (start_pos, _) = maze
        .things
        .iter()
        .find(|(_point, val)| **val == '@')
        .unwrap();

    bfs_keys(maze, &[*start_pos])
}

mif from within the function

I expected this to happen:

fn part_1(maze: &Maze) -> usize {
>    let (start_pos, _) = maze
>       .things
>        .iter()
>        .find(|(_point, val)| **val == '@')
>      .unwrap();
>
>  bfs_keys(maze, &[*start_pos])
}

Instead, this happened:

fn part_1(maze: &Maze) -> usize > {
>    let (start_pos, _) = maze
>       .things
>        .iter()
>        .find(|(_point, val)| **val == '@')
>      .unwrap();
>
>  bfs_keys(maze, &[*start_pos])
> }

where ">" represents a selection

Helix log

~/.cache/helix/helix.log

please provide a copy of `~/.cache/helix/helix.log` here if possible, you may need to redact some of the lines

Platform

Linux

Terminal Emulator

alacritty

Installation Method

source

Helix Version

helix 25.01.1 (e7ac2fc)

[woojiq]

1. Tree-sitter is responsible for the bounds selection, not rust-analyzer (just fyi)
2. How it should work with this function work then?

fn main() { println!("test"); }

Personally, I like the current behavior as it is consistent with other mi* functions.

[pascalkuthe]

Yeah this is intentional

[abrassel]

Practically speaking, I usually want to copy the body of the function. When mif also inherits the brackets, I will have to trim them later.

Is there an alternate behavior for my intended use case?