lsif-clang
bar
lsif-clang | bar | |
---|---|---|
4 | 12 | |
33 | - | |
- | - | |
0.0 | - | |
about 1 year ago | - | |
C++ | ||
- | - |
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.
bar
-
Teller: Universal secret manager, never leave your terminal to use secrets
$ pass git remote add origin https://github.com/foo/bar.git
-
Can someone explain me esily how to use an existing Github repo locally?
git clone https://github.com/foo/bar /some/directory. Even better, set up ssh keypair and clone via ssh, so you don't need to type your username and password each time you push. The correct address will be on GitHub, under green Clone button, just change it from https to ssh.
-
The technology behind GitHub’s new code search
Yes, just change the URL from https://github.com/foo/bar to https://sourcegraph.com/github.com/foo/bar to be dropped in to a code search for that GH repo.
-
Information of or automatic updates from github repos?
nchecker. Also, https://github.com/foo/bar/releases.atom
-
Show HN: Personal productivity workspace for busy people
This seems very good.
1. This looks like Notion, which is good. Notion succeeded by being pretty.
2. It feels...I don't know the way to say it, but the appropriately level of solid (I don't accidentally drag and drop stuff), fast, and just easy to use. No non-modal mix of commands and typing makes entering information frustrating. It feels like typing into Notepad. It's frustration-free.
3. I would like if the dashboard showed unscheduled tasks (as a collapsible section at the very bottom, below Completed.)
4. I have TODOs of the form "Deploy XYZ" and ideally they would be "Deploy XYZ - https://github.com/foo/bar/pull/1337" -- but this adds a lot of clutter to the task list. If there were a way to add details or attach notes to tasks, that would be helpful. (It would also add clutter, so be careful. Just a "Details" link next to "Schedule" and the tags might work. Make it open a note on the right, perhaps?)
5. The "Schedule" link below each item makes me think I haven't scheduled the item, but I have. It should say "Today" (when I'm looking at today on the dashboard).
6. The importing of calendars scared me as it populated a giant list, including my coworkers calendars that I've subscribed to (but have set to not display), but turned out fine. Only the ones I have set to display in Google Calendar display in Emery by default. The import UX maaaaybe could be better / less aggressive, but it works.
7. The dichotomy between "schedule this for today" and "add this to a specific time on my calendar" still exists, and frustrates me, but the ability to sort the tasks helps.
8. It's good that this is opinionated. Stay focused and reject most feature requests, including mine.
9. You got me to enter my credit card before I even got to play around with it. That's impressive, but you are definitely cutting your top-of-funnel with that requirement. (Maybe it pays off by increasing conversion at the free trial->paid step, or maybe you only want true believers at the beginning, but the payment form would usually have turned me away.)
10. Can I export my data? In seven days, am I going to have to manually copy-and-paste all my notes and outstanding TODOs back into my old system if I decide this isn't for me? This risk also makes me hesitant to go all-in during the trial period. (An export wouldn't fully solve this, since I'd then have a messy JSON file or something to deal with, but I'd feel a little better about it.)
-
Best way to work on a composer package (library) while it's being used inside of a project?
Thank you, I tested this and it looks very promising. It does in fact change the composer.json accordingly, so I can use this command instead of hand-editing the json file. This means that I have commit to my git repo a `path` repository pointing to my dev package, but in my Dockerfile for production build I can run composer config repositories.foo vcs https://github.com/foo/bar to change "foo" on the fly to something else (e.g. git)
-
Commenting code: yes or no?
// We have to discard the first read of this sensor because of a know bug // in its firmware. Remove the redundant read after this issue has been resolved: // https://github.com/foo/bar/issues/10 temperatureSensor.read(); let temp = temperatureSensor.read();
-
Code online always starts with $?
$ git clone https://github.com/foo/bar.git
-
Improving GitHub Code Search
The best thing about the Sourcegraph instance hosted on sourcegraph.com is that you can edit the URL in your browser from https://github.com/foo/bar to https://sourcegraph.com/github.com/foo/bar to be dropped down into a Sourcegraph search for that GH repo. I've been using it for a long time because of this convenience.
(Though it would be even better if the two options for case-sensitivity and regex search were enabled by default instead of needing me to toggle them on every time.)
-
Git as a Storage
> I think you can get the wiki with plain old 'git' ? I forget ...
This is correct. The wiki for a repo is accessible as a separate repository named with a suffix of “.wiki”.
So if user foo has a repo bar with an associated wiki, and the repo URL is https://github.com/foo/bar then you can clone the repo and the wiki respectively over SSH by:
git clone [email protected]:foo/bar.git
What are some alternatives?
cppinsights - C++ Insights - See your source code with the eyes of a compiler
nvchecker - New version checker for software releases
codechecker - CodeChecker is an analyzer tooling, defect database and viewer extension for the Clang Static Analyzer and Clang Tidy
mozsearch - Mozilla code search website. (Please file bugs in bugzilla at https://mzl.la/2YtXmoN)
scip - SCIP Code Intelligence Protocol
zoekt - Fast trigram based code search
color_coded - A vim plugin for libclang-based highlighting of C, C++, ObjC
gitlab
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.
stack-graphs - Rust implementation of stack graphs
advanced
feedback - Public feedback discussions for: GitHub for Mobile, GitHub Discussions, GitHub Codespaces, GitHub Sponsors, GitHub Issues and more! [Moved to: https://github.com/github-community/community]