科技回声

For something less PoCy, <a href="https://www.sourcetrail.com/" rel="nofollow">https://www.sourcetrail.com/</a> 's internal representation of the reference graph is a sqlite db file with pretty much a triple store schema.

Man. I love SQLite, but the current virtual table extension is a performance dumpster fire. SQLite doesn’t understand multiple-column indexes on virtual tables, and the secret sauce to make it pick the “best” index is found only in the Necronimicon. Inevitably, with even fairly trivial joins, SQLite bails out to a polynomial sequential scan.

I tried doing this using prolog last summer to extract some features from a codebase. I loved it. Being able to query a codebase like a database is extremely useful.

Pretty cool! One question though: if this was based on LSP in general, it could be generalised to any language, right? I wonder why they wired it to clangd specifically.

Cscope as a SQL DB? I would really like that. But it's important not to stop at parsed code, especially in C (for obvious reasons).

This is cool! You can do a lot of things with SQLite these days.

I tried doing this using prolog last summer to extract some features from a codebase. I loved it. Being able to query a codebase like a database is extremely useful.

Pretty cool! One question though: if this was based on LSP in general, it could be generalised to any language, right? I wonder why they wired it to clangd specifically.

Cscope as a SQL DB? I would really like that. But it's important not to stop at parsed code, especially in C (for obvious reasons).

This is cool! You can do a lot of things with SQLite these days.

Show HN: ClangQL – Query C++ codebases using SQLite

6 条评论

Show HN: ClangQL – Query C++ codebases using SQLite

6 条评论