tree-sitter-kotlin
tree-sitter-kotlin copied to clipboard
Kotlin grammar for Tree-sitter
https://github.com/fwcd/tree-sitter-kotlin/blob/2878163ee7cad7eaebd3df1729e86610891fe0ee/bindings/rust/lib.rs#L41
I have a variable called `isEligible`. When I write `return !isEligible`, it gets parsed as a call to `!is` with a class called `Eligible` instead of a variable. ```kotlin return...
**Current behavior:** Suppose that I had a class that looked like this: ``` public class Foo constructor () { < stuff in here > } ``` This is meant to...
I think the parsing result in the return statement is incorrect in the following example. ![image](https://user-images.githubusercontent.com/48522331/228198499-b99b3338-d662-4e81-a4d0-310bc572e5f2.png) It is expected that it can be parsed into an additive expression. Like this...
Source: ```kotlin infix fun Int.oppa(a: Int) { } fun main() { 1 oppa 4 } ```
code like below will not parse correctly, due to the comment line inside the code block inside the multiline comment: /** * * ```kotlin * object Foo { * /**...
There is an error parsing functional interfaces. For example (from kotlinlang.org): ```kotlin fun interface IntPredicate { fun accept(i: Int): Boolean } ``` The node which should represent the body/`accept` method...
I observed that in current main an expression like ```kt !x || y ``` gets parsed as `prefix_expression(disjunction_expression ...` . In the tree-sitter web playground hosted [online](https://fwcd.github.io/tree-sitter-kotlin) it is correctly...
New PRs regularly fail the CI check that verifies that the generated parser matches the committed `parser.c`, presumably because their development machine didn't generate a byte-for-byte-exact copy of the parser...