lsif-go
scip
lsif-go | scip | |
---|---|---|
6 | 7 | |
114 | 222 | |
- | 5.4% | |
10.0 | 7.3 | |
8 months ago | 12 days ago | |
Go | Rust | |
MIT License | 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.
lsif-go
-
srctx: A golang library for automatically evaluating the function level impacts of Git Diff
curl -L https://github.com/sourcegraph/lsif-go/releases/download/v1.9.3/src_linux_amd64 -o /usr/local/bin/lsif-go chmod +x /usr/local/bin/lsif-go lsif-go -v
-
Codegraph – static code analyzator / code diagramer
Very nice. For those interested, you can get similar information using SourceGraph and LSIF in a standardized, language agnostic form: https://lsif.dev/. It still generally requires build information for each project/language, unfortunately.
- srctx: a LSIF parser for understanding what happened in every lines of your code
- Steve Yegge Joins as Head of Engineering of Sourcegraph
-
“Zoom Out”: The missing feature of IDEs
Doing it as a comment would be pretty awful. But anyway I guess the author is looking for https://lsif.dev/
-
Byfrost Indexer working with Go
If you want an example of using go compiler frontend for static analysis, checkout https://github.com/sourcegraph/lsif-go, this powers our precise code navigation indexing for Go and solves your issue of not having type information when using tree-sitter (the code is a bit hard to follow because a lot of work went into making it as fast as possible, but feel free to find your way to our Discord where we could answer questions). Dont try to reimplement type checking, its all there waiting to be used ; )
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.
What are some alternatives?
codegraph - CodeGraph - Tool that create a graph of code to show dependencies between code entities (methods, classes and etc).
lsif-clang - Language Server Indexing Format (LSIF) generator for C, C++ and Objective C
difftastic - a structural diff that understands syntax 🟥🟩
cargo-udeps - Find unused dependencies in Cargo.toml
codequery - A code-understanding, code-browsing or code-search tool. This is a tool to index, then query or search C, C++, Java, Python, Ruby, Go and Javascript source code. It builds upon the databases of cscope and ctags, and provides a nice GUI tool.
cargo-semver-checks - Scan your Rust crate for semver violations.
emerge - Emerge is a browser-based interactive codebase and dependency visualization tool for many different programming languages. It supports some basic code quality and graph metrics and provides a simple and intuitive way to explore and analyze a codebase by using graph structures.
hn-search - Hacker News Search
community - Issue tracker for the community team at Sourcegraph
rust-analyzer - A Rust compiler front-end for IDEs
IDE-Block - GitHub Block providing IDE-like features to help you read code.
zig-hcs-client - A simple REPL for controlling Zig's hot-code swapping compilation mode