Gears
Gears
Probably, yes. Also, you'll want to add tests for this new warning. And in the issue I mentioned adding a code action to fix this warning. Do you think you...
> The code action should be implemented in the lsp area of the repository? Correct. It should be in the `language_server/code_action.rs` file. You can look at the `code_action_unused_imports` function (which...
> @GearsDatapacks can you suggest any example of a single case simplification where the pattern is not a constructor? For example, ```gleam case my_tuple { #(a, b) -> do_stuff(a, b)...
I've just realised something which might make this code action a little more complex. What do you expect to happen if you run the code action on: ```gleam let v...
Perhaps not. It could still me useful in some cases, but I imagine the majority will be using let assignment to extract values. Maybe this should just be a warning...
I can't reproduce this on 1.5.0 with VSCode. Can someone try this with neovim to see if it still occurs?
Thank you! Go for it
Looks good so far. Since this PR isn't ready to be merged yet, would you mind converting it to a draft?
At some point yes, although this won't be merged until 1.9 is released. Make sure to rebase, as merge commits are not allowed in this codebase
Hopefully the functionality of the `constructor_index` field should be clearer now