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
{{ message }}
This repository was archived by the owner on Sep 9, 2025. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 9, 2025. It is now read-only.
This could be considered a bug or a feature I suppose, but I was certainly surprised that an error in my .tsg prevented me from successfully running cargo run -p tree-sitter-stack-graphs-java -- parse file.java.
That's an interesting one. I agree that ideally it wouldn't fail. Butt the way the project is setup, I'm not sure it can easily be avoided.
The generic tree-sitter-stwck-graphs command that loads things from the file system wouldn't fail I think. But in the specialized tssg-java command, the language configuration is built up in memory before being used, and it's a little more eager.
The github/stack-graphs repository is no longer being maintained. As per #502, I'm closing all issues and pull requests before archiving the repository.
Activity
hendrikvanantwerpen commentedon Jan 13, 2023
That's an interesting one. I agree that ideally it wouldn't fail. Butt the way the project is setup, I'm not sure it can easily be avoided.
The generic tree-sitter-stwck-graphs command that loads things from the file system wouldn't fail I think. But in the specialized tssg-java command, the language configuration is built up in memory before being used, and it's a little more eager.
hendrikvanantwerpen commentedon Feb 2, 2023
Leaving a reference to https://docs.rs/lazy-init/latest/lazy_init/ here, in case we consider lazy rule parsing in language configurations.
[-]Parsing runs tsg rules[/-][+]`parse` command parses unused TSG rules[/+]dcreager commentedon Feb 2, 2023
I think
once_cellis preferred these days for all things lazily initialized.CleanCut commentedon Sep 9, 2025
The github/stack-graphs repository is no longer being maintained. As per #502, I'm closing all issues and pull requests before archiving the repository.