scip
stack-graphs
scip | stack-graphs | |
---|---|---|
7 | 6 | |
222 | 694 | |
5.4% | 1.9% | |
7.3 | 9.6 | |
13 days ago | 7 days ago | |
Rust | Rust | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
scip
-
Show HN: GritQL, a Rust CLI for rewriting source code
security is up there, but from reading the examples in CodeQL it just seemed like it would be possible to express some truly great versions of "don't do that" rules in it. I am a total JetBrains fanboi, and their introspections are world-class, but getting Qodana to run to completion before the heat death of the universe has proven to require more glucose than I have to offer it. Thus, I'm always interested in alternate implementations, even though I am acutely aware of the computational complexity of what I'm asking
I recalled another link I wish I had included in my question from the SourceGraph folks https://github.com/sourcegraph/scip#scip-code-intelligence-p... which started out life as "Language Server Indexing Protocol" and seems to solve some similar project-wide introspection questions but TBH since their rug pull I've been a lot less willing to hitch my wagon to their train
-
Have questions/requests/issues related to the Zig Language Server?
New standards proliferate all the time and many simply cannot rely solely on a compiler language server but can rely on a custom semantic information protocol - SCIP comes to mind. :)
-
srctx: a LSIF parser for understanding what happened in every lines of your code
Over the last ~9 months or so, we've been moving away from LSIF and have been using SCIP instead. https://github.com/sourcegraph/scip (announcement blog post, which covers the reasons for why we stopped using LSIF: https://about.sourcegraph.com/blog/announcing-scip)
-
The technology behind GitHub’s new code search
This is pretty much exactly what we've built at Sourcegraph. Microsoft had introduced (but pretty much abandoned before it even started) LSIF, a static index format for LSP servers requests/responses.
We took that torch and carried it forward, building the spiritual successor called SCIP[0]. It's language agnostic, we have indexers for quite a few languages already, and we genuinely intend for it to be vendor neutral / a proper OSS project[1].
[0] https://about.sourcegraph.com/blog/announcing-scip
[1] https://github.com/sourcegraph/scip
-
Steve Yegge Joins as Head of Engineering of Sourcegraph
Created a PR to mention tools using SCIP in the README. https://github.com/sourcegraph/scip/pull/101
-
cargo-udeps 0.1.33 release
I've looked into the pull request that added SCIP support to rust-analyzer, and apparently rust-analyzer uses the scip crate. The linked PR also links to a blog post that explains the motivation for scip. The github repo of the scip crate lives here, it's not linked in Cargo.toml, probably should.
stack-graphs
-
Code Search Is Hard
https://github.com/pyjarrett/septum
The hardest part about getting code search right imo is grabbing the right amount of surrounding context, which septum is aimed at solving on a per-file basis.
Another one I'm surprised hasn't been mentioned is stack-graphs (https://github.com/github/stack-graphs), which tries to incrementally resolve symbolic relationships across the whole codebase. It powers github's cross-file precise indexing and conceptually makes a lot of sense, though I've struggled to get the open source version to work
-
Even the Pylint codebase uses Ruff
[2]: https://github.com/github/stack-graphs
-
The technology behind GitHub’s new code search
> It doesn't have the faintest idea where the name is defined, or if there's even a difference between a function name, a parameter name, or a word in a comment.
I don't think what you are saying is actually true for stack-graphs[0][1].
[0]: https://github.com/github/stack-graphs
[1]: https://github.blog/2021-12-09-introducing-stack-graphs/
-
Should I be worried or not worried about Tree-sitter now that the Atom editor has been killed?
I think GitHub still has some use for tree-sitter. In this post it's mentioned that their new code navigation system is based on tree-sitter. In a more recent post they welcome contributers to add special code navigation queries to existing languages. You can find their public repository here if you want to follow along with any developments. Since their code navigation system relies heavily on tree-sitter I don't think it's going anywhere soon (fingers crossed).
-
What happened with GitHub's semantic project?
Which they implement in Rust. https://github.com/github/stack-graphs
-
Stack Graphs
As mentioned elsewhere on this thread, stack graphs and Semantic were built by the same team (which I manage). Semantic is not abandoned, we've just been focusing on a different layer of our tech stack for the past year or so. https://news.ycombinator.com/item?id=29501389
That PR on the Semantic repo was our first attempt at implementing these ideas. We decided to reimplement it in a separate library (also open source, https://github.com/github/stack-graphs), which only builds on tree-sitter directly so that there's an easier story for us and language communities to add support for new languages. It's a fair point that we could have closed the Semantic PR to indicate that more clearly.
What are some alternatives?
lsif-clang - Language Server Indexing Format (LSIF) generator for C, C++ and Objective C
semantic-source - Parsing, analyzing, and comparing source code across many languages
cargo-udeps - Find unused dependencies in Cargo.toml
kickstart.nvim - A launch point for your personal nvim configuration
cargo-semver-checks - Scan your Rust crate for semver violations.
nvim-lspconfig - Quickstart configs for Nvim LSP
lsif-go - Language Server Indexing Format (LSIF) generator for Go
scip-zig - SCIP indexer for Zig!
hn-search - Hacker News Search
pagefind - Static low-bandwidth search at scale
rust-analyzer - A Rust compiler front-end for IDEs
nvim-ts-context-commentstring - Neovim treesitter plugin for setting the commentstring based on the cursor location in a file.