diff options
| author | 2026-06-24 05:38:13 +0000 | |
|---|---|---|
| committer | 2026-06-24 05:50:17 +0000 | |
| commit | 073b18ae21b33c578a57700ee3d9c6d7fb2080be (patch) | |
| tree | 74af2c1f5a3fb507bbcc0a1840ce4b0b676b0c0d | |
| parent | Disable ireturn (diff) | |
TODO
| -rw-r--r-- | TODO | 12 |
1 files changed, 1 insertions, 11 deletions
@@ -1,7 +1,7 @@ * The append functions are not transactional. Or perhaps we should make them transactional? -* Perhaps no GIGO in serialization +* Perhaps no GIGO in serialization * Too strict about tagger? @@ -12,16 +12,6 @@ * Check error wrapping in object/fetch * Pack ingestion - * v2 resolver: explicit work-stack with evicting clock.Clock base cache - bounds base-object memory so a zlib-bomb base can't OOM us - needed for parallelism - * Incremental thin completion: append one base then cascade, like git, - instead of batch collecting then cascade, maybe? - * Partial promote orphan cleanup; audit contract too - * Strict mode or otherwise structurally validate trees/commits/tags * SHA-1 collision detection - * Accept a context - * Multithreading - * Over-read footgun * which object ID length mismatches should panic vs error |
