chore: Switch to tree-sitter-java-orchard
#546
No reviewers
Labels
No labels
Compat/Breaking
Kind
Bad merge
Kind
Bug
Kind
Documentation
Kind
Enhancement
Kind
Feature
Kind
New language
Kind
Security
Kind
Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: mergiraf/mergiraf#546
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "540-upgrade-java-parser"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fixes a bunch of parsing failures and introduces fields for #540.
@ -1,3 +1,3 @@
class Cls {
final protected static void method() {}
This is linked to #545. I plan to revisit this later.
@ -135,4 +120,0 @@
"non-sealed",
],
" ",
),
Nice simplification due to https://github.com/tree-sitter/tree-sitter-java/pull/211 which I integrated in the fork.
@ -549,2 +549,2 @@
assert_eq!(matching.recovery.len(), 18);
assert_eq!(matching.full.len(), 39);
assert_eq!(matching.recovery.len(), 20);
assert_eq!(matching.full.len(), 41);
This is a side-effect of https://github.com/tree-sitter/tree-sitter-java/pull/211.
Interestingly, this seems to have caused a significant slowdown… I'm not sure if it's because my computer was more busy when I ran the second benchmark, of if it's a real issue.
And it's a bit disappointing that it's only solving one parse error. I'll investigate at some point.
*.java
So, I have some good news: the timing difference is spurious, due to me suspending my computer during the benchmark and it inflating the running time of one example. The updated table is:
*.java
Then, another piece of "good" news, is that the case that changed from "Conflict" to "Panic" with this change is a new type of panic we didn't know before!
It probably doesn't have much to do with the grammar update on its own and probably happens in other circumstances, so I'm excited that the benchmark picked it up. And I get to use the minimizer again, yay!
9bb6ae70f9
toa9b415fee6
I have run a new benchmark after rebasing on top of main and adding the signature for
annotation_marker
nodes. The picture is quite different!*.java
The good news is that the change is now entirely positive (only numbers below the diagonal), with mergiraf only solving more conflicts in ways that are consistent with the observed merges.
The panic noticed above is still happening, both before and after this PR. So I think we can merge this and handle the panic separately (I'm on it).
Oh, very nice!