lsif-clang
scip-clang
lsif-clang | scip-clang | |
---|---|---|
4 | 2 | |
33 | 42 | |
- | - | |
0.0 | 7.6 | |
about 1 year ago | 15 days ago | |
C++ | C++ | |
- | 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-clang
-
The technology behind GitHub’s new code search
In the top right corner of the tooltip it will say either "Search-based" or "Precise" - in this case, you're right, we don't have the abseil-cpp repo indexed so it falls back to search-based as you describe.
We do have a C++ code indexer in beta, https://github.com/sourcegraph/lsif-clang - it is based on clang but C++ indexing is notably harder to do automatically/without-setup due to the varying build systems that need to be understood in order to invoke the compiler.
-
GitHub Code Search (Preview)
Interesting because on https://lsif.dev/ I see that LSIF support for C++, which basically is just a wrapper around clangd AFAIU, is deprecated. Is there something else that replaced it?
-
SCIP - a better code indexing format than LSIF
We already have an LSIF indexer for C++ (lsif-clang); however, that is not as feature complete as the other indexers. Moreover, the codebase is forked off of Clang 10, so upgrading to newer Clang versions (and build a SCIP indexer on top of that) will be a challenge.
-
Google Is 2B Lines of Code–and It's All in One Place
- Go:
Why are not all repos covered?
Because different languages have different build systems, so inferring the right build commands, dependencies etc. is not so straightforward; these are necessary per-requisites for compiler-accurate cross references. We're working on fixing this with auto-indexing: https://docs.sourcegraph.com/code_intelligence/explanations/...
For C and C++ specifically, auto-indexing is challenging because of the large variety in build systems, informal specification of dependencies (such as in a README instead of a machine-readable format), and platform-specific code.
Outside of auto-indexing, we do have an indexer for C and C++ right now (https://github.com/sourcegraph/lsif-clang) which can be run in CI; that way one can generate an index and upload it to Sourcegraph on a regular basis. It is 'Partially available' (https://docs.sourcegraph.com/code_intelligence/references/in...) right now. We're keenly aware of the interest in C++, and are working our way through different languages based on usage.
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.
What are some alternatives?
cppinsights - C++ Insights - See your source code with the eyes of a compiler
sg.nvim - Experimental Sourcegraph + Cody plugin for Neovim
codechecker - CodeChecker is an analyzer tooling, defect database and viewer extension for the Clang Static Analyzer and Clang Tidy
llvm-project - The LLVM Project is a collection of modular and reusable compiler and toolchain technologies.
scip - SCIP Code Intelligence Protocol
stack-graphs - Rust implementation of stack graphs
color_coded - A vim plugin for libclang-based highlighting of C, C++, ObjC
sourcegraph - Code AI platform with Code Search & Cody
LLVM-Guide - LLVM (Low Level Virtual Machine) Guide. Learn all about the compiler infrastructure, which is designed for compile-time, link-time, run-time, and "idle-time" optimization of programs. Originally implemented for C/C++ , though, has a variety of front-ends, including Java, Python, etc.
advanced
Bazel - a fast, scalable, multi-language and extensible build system