Don't autoclose angle brackets

[x4132]

Previously whenever a condition such as < was typed the corresponding closing bracket would also be autocompleted, this is extremely annoying and unhelpful for users. This disables autoclose. For class instantiation autocomplete already autocloses the closing bracket.

[tartarughina]

I think that providing an option for not_in is a better approach.
Are we able though to understand from tree-sitter when auto closing should or shouldn't be enabled?

Auto closing of angled brackets, even if limited, is a nice feature to have. But if inequalities cannot be isolated then let's consider the other instances where < is going to be used before committing the change.

[x4132]

I think that providing an option for not_in is a better approach. Are we able though to understand from tree-sitter when auto closing should or shouldn't be enabled?

I don't think angle bracket pairs are used for anything except generics in Java, while individual angle brackets are obviously used for comparisons. I would agree that adding not_in rules would be better, but there are a lot more edge cases to think about first.

For example, differentiating between the following two lines:

ArrayList<Integer> foo = new ArrayList<>(); boolean bar = 1 < 2;

It's definitely possible but will take a lot more effort, definitely easier ones such as if statements or strings can be added but having rules for the other ones might be more difficult. Is there the opposite (an in rule) instead?

[playdohface]

We can add autoclosing generics-brackets, but for the time being I think this makes sense