scip-clang
scip
scip-clang | scip | |
---|---|---|
2 | 7 | |
42 | 222 | |
- | 4.1% | |
7.6 | 7.3 | |
8 days ago | 8 days ago | |
C++ | 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-clang
-
scip-clang: A new code indexer for C++
Use clangd as a library downstream, instead of directly using Clang - This could've potentially worked, but the problem is that it adds one more layer of indirection for understanding and debugging, which isn't necessarily a win just to get some more code reuse. I've read through some of the clangd code to see if we should adjust our own code. E.g. this bug fix is based on how clangd handles unresolved dependent names: https://github.com/sourcegraph/scip-clang/pull/321
-
The technology behind GitHub’s new code search
(I work on C++ indexing at Sourcegraph.)
As my colleague mentioned in a sibling comment, we have an existing indexer lsif-clang which supports C++. I just added a Chromium example to the lsif-clang README right now: (direct link) https://sourcegraph.com/github.com/chromium/chromium@cab0660...
We are also actively working on a new SCIP indexer which should support features like cross-repo references in the future. https://github.com/sourcegraph/scip-clang
Right now, Abseil doesn't have precise code navigation because no one has uploaded an index for it. In an ideal world, we would automatically have precise indexes for all the C++ code on Sourcegraph, but that's a hard problem because of the large variety in build systems, build configurations, and system dependencies that are often specified outside the build system.
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?
lsif-clang - Language Server Indexing Format (LSIF) generator for C, C++ and Objective C
sg.nvim - Experimental Sourcegraph + Cody plugin for Neovim
cargo-udeps - Find unused dependencies in Cargo.toml
llvm-project - The LLVM Project is a collection of modular and reusable compiler and toolchain technologies.
cargo-semver-checks - Scan your Rust crate for semver violations.
stack-graphs - Rust implementation of stack graphs
lsif-go - Language Server Indexing Format (LSIF) generator for Go
sourcegraph - Code AI platform with Code Search & Cody
hn-search - Hacker News Search
rust-analyzer - A Rust compiler front-end for IDEs
zig-hcs-client - A simple REPL for controlling Zig's hot-code swapping compilation mode