You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm opening this issue to let the maintainers know that we're planning to merge a change to the tree-sitter-clojure master branch that might be of interest to this repository.
So if that assessment is correct and the dependency doesn't change it seems our intended upcoming change shouldn't have any effect.
However, the change should also address sogaiu/tree-sitter-clojure#21 which Wilfred reported to us earlier, so may be there would be some interest in using the updated code?
Please let us know if you decide to try the new code as well as if you encounter any issues.
Thanks!
P.S. Our current plan is to merge around 2023-01-05 which is in about 2 weeks time.
On a more general note...
Though at this time we don't anticipate many changes going forward, we're planning to post certain change-related announcements to a pinned issue ahead of merging such changes.
Please have a look at the issue and consider subscribing :)
The text was updated successfully, but these errors were encountered:
I'm opening this issue to let the maintainers know that we're planning to merge a change to the tree-sitter-clojure master branch that might be of interest to this repository.
The change is here: sogaiu/tree-sitter-clojure#31
A brief overview of the changes follows.
kwd_lit
andsym_lit
will now contain up to 3 new nodes:Only the
(kwd_name)
and(sym_name)
are required.sym_lit
nodes can still contain metadata nodes (this is unchanged).IIUC, difftastic currently uses a commit on the issue-21 branch of tree-sitter-clojure -- at least it seems so according to:
So if that assessment is correct and the dependency doesn't change it seems our intended upcoming change shouldn't have any effect.
However, the change should also address sogaiu/tree-sitter-clojure#21 which Wilfred reported to us earlier, so may be there would be some interest in using the updated code?
Please let us know if you decide to try the new code as well as if you encounter any issues.
Thanks!
P.S. Our current plan is to merge around 2023-01-05 which is in about 2 weeks time.
On a more general note...
Though at this time we don't anticipate many changes going forward, we're planning to post certain change-related announcements to a pinned issue ahead of merging such changes.
Please have a look at the issue and consider subscribing :)
The text was updated successfully, but these errors were encountered: