diff options
| author | Pjotr Prins <pjotr.public01@thebird.nl> | 2026-11-16 16:35:24 +0000 |
|---|---|---|
| committer | Pjotr Prins <pjotr.public01@thebird.nl> | 2026-11-16 16:35:24 +0000 |
| commit | d5e90011f764ba27251936d4fa628e1100145773 (patch) | |
| tree | 0f671a2b19bb24af91201776746b8e6d511eb95b /schema.sql | |
| parent | dc4c16203674191c4821b2f7b53e01febb7a11a6 (diff) | |
| download | ai-memory-d5e90011f764ba27251936d4fa628e1100145773.tar.gz | |
symbols: C and C++ declarations from ctags, diffed between blobs
C and C++ were the one language family where the store could only say "a hunk
landed inside this function". A diff line cannot be read for declarations
there: inside a body `foo(bar);` calls something, inside a class body the same
bytes declare a constructor, and pangemma indents both the same way (of 248538
changed lines in its history, 14991 are indented `name(` lines, and the most
frequent are calls). So the file is handed to universal-ctags and the tags of a
commit's blob are diffed against its parent's: present only in the new blob is
an add, only in the old one is a remove, and a name whose tag survives both is
left to hunk context, which is the honest answer for "the change was inside
this".
The cost is bounded by a cache keyed by git object id (new table `blobs`): a
blob's tags can never change, so each file version is parsed once per store.
On the pangemma history (688 commits, 1163 distinct C/C++ blobs) the first full
pass takes 26 s and touches go from 1404 context-only rows to 6888 add, 5125
remove, 1505 context; the second pass takes 11 s and runs no ctags at all.
ctags is optional at run time. Without it the store behaves exactly as before
and `sync` says so once. The Guix package bakes its absolute path into
$AI_MEMORY_CTAGS through wrap-program, and the check phase now builds a
two-commit git repository with one C++ file to prove it end to end: the
function added in the second commit is `add`, the one whose body changed is
`context`.
Details found by running it on a real history, all in this commit:
- lambdas are tagged by default under names ctags derives from a hash of the
file (`__anon426fc91f0102`), so every touched file reported seven functions
added and seven removed per commit; `--extras=-{anonymous}` turns them off.
- `--kinds-C++=+p` is needed or prototypes are invisible and a declaration in a
header would never be seen.
- include guards (`#define CALC_H`, `#define __CALC_H__`) are filtered: they are
bookkeeping, while other macros are kept as `const`.
- merge_decl keyed a commit's declarations by bare identifier, so two files
declaring the same name in one commit collided and one lost its attribution.
It is keyed by (file, name) now -- a bug that applied to Odin and Rust too.
Diffstat (limited to 'schema.sql')
| -rw-r--r-- | schema.sql | 14 |
1 files changed, 12 insertions, 2 deletions
diff --git a/schema.sql b/schema.sql index e624369..1d38f7a 100644 --- a/schema.sql +++ b/schema.sql @@ -1,4 +1,4 @@ --- ai-memory schema, version 3. +-- ai-memory schema, version 6. -- -- commits : one row per git commit, derived from `git log' by `sync'. -- symbols : one declared identifier per row (proc, fn, type, const, var). @@ -63,6 +63,16 @@ create index if not exists symbol_basename_idx on symbols (basename); -- `log' walks commits newest-first; the index lets it stop after LIMIT rows. create index if not exists commit_ts_idx on commits (author_ts); +-- blobs: the C/C++ declaration cache. One row per git blob that ctags has +-- parsed, keyed by object id, holding that blob's tags as "<ctags kind>\t<name>" +-- lines. A blob's content cannot change, so a row can never go stale; this is +-- purely a speed cache -- drop the table and the next `sync' re-derives it in a +-- couple of ctags runs per new file version instead of one per commit per file. +create table if not exists blobs ( + blob text primary key, + tags text not null +); + create virtual table if not exists reasoning_fts using fts5 ( body, content = 'reasoning', content_rowid = 'id' ); @@ -80,4 +90,4 @@ create trigger if not exists reasoning_after_update after update on reasoning be insert into reasoning_fts (rowid, body) values (new.id, new.body); end; -pragma user_version = 5; +pragma user_version = 6; |
