Thanks so much for this! IMO this is a huge usability improvement.

I stopped working on the Scala grammar due to the frustration with the total ordering. With this I think I'll start working on it again.

That's great to hear!

This seems to be missing from the dsl types?

/// <reference types="tree-sitter-cli/dsl" />
// @ts-check

Causes this to error

/// <reference types="tree-sitter-cli/dsl" />
// @ts-check

@razzeee could you tell where do you usually put such lines? Is it globals.d.ts file or somewhere else?

Top of your grammar file. I just have one which is grammar.js

https://www.github.com/elm-tooling/tree-sitter-elm/tree/master/grammar.js

Thanks for the heads up @razzeee.

seems to be missing from the dsl types?

Fixed on master.

It would be nice if commenting a partial ordering relation on precedence showed a conflict example, like it happens when commenting a tuple of rules on conflicts. I find the "Unresolved conflict" message useful to remember the conflicts.

I've been using the following strategy to workaround the "Undeclared precedence" error:

//['foo', 'bar']
['foo']
['bar']

Maybe the "Unresolved conflict" could be thrown after "Undeclared precedence" error?

By the way, I appreciate the implementation of this elegant solution for the precedence problem.

Ok, an update on this - In Tree-sitter v0.19.1, I've added a feature make the partial orderings easier to specify. You can control the precedence of an entire grammar rule by including a reference to the rule (using the $.my_rule syntax) directly in the precedences list.

For example, in JavaScript, to control the precedence of await expression and arrow functions relative to binary operators, you can simply do this:

precedences: $ => [
  [
    'binary_times',
    'binary_plus',
    // ...
    $.await_expression,
    $.arrow_function
  ],
],

I'll write up more documentation on this in the main docs site soon.

This is a great change; looking forward to using it. I had already been trying to do something like this (very informally) myself 😄 :

const PRECEDENCE = {
    //...
    // Prefer `type_identifier` after the colon in '{ ( identifier : identifier'
    type_over_primary: 1,
    // Prefer `parameter_list` over `void_type` in `func f(_: () -> Foo)`
    param_over_void: 1,
    // Prefer expression _patterns_ over bare expressions
    pattern_over_expr: 1,
    // ...
}

Also need to update the file ´cli/src/generate/grammar-schema.json´ to include the precedences key.

This is a great feature and should be included in the documentations.