4 ms·
Yea that would be Kythe. We build almost everything, across 44-45 different programming languages, and postprocess that into a giant semantic graph. Most majo
by dmoy 3y ago
Yea that would be Kythe. We build almost everything, across 44-45 different programming languages, and postprocess that into a giant semantic graph.
Most major parts are open sourced at kythe.io, and there's a somewhat dated talk given by Luke here: https://youtu.be/VYI3ji8aSM0 https://youtu.be/VYI3ji8aSM0
- dmoy 3y ago> macros Corollary: while we can do a lot with indexing generated code (even cross language) in Kythe, there are limits. Macros may be one, I forget atm
- sa46 3y agoDo you have any cases studies or success stories for non-Google repos? I miss code search but I’m not sure how close Kythe is to code-search-in-a-box.
- dmoy 3y agoInternally, we use variants of our pipeline to index a variety of open source repos, and some non-blaze/bazel internal repos. Those are often non-Google repos. But we're using some internal postprocessing and serving logic to actually create and host the final index. Unfortunately I don't know if there's any significant use of Kythe outside of Google. We get a handful of questions on the open source repo from time to time, but that's all I know about.