]> git.giacomolli.uk - onechat/commit
Name and order the memory core code
authorAnderson A. Giacomolli <agiacomolli@gmail.com>
Sat, 7 Nov 2026 17:10:33 +0000 (14:10 -0300)
committerAnderson A. Giacomolli <agiacomolli@gmail.com>
Sat, 7 Nov 2026 17:10:33 +0000 (14:10 -0300)
commitbaf7a940be8927278e3b4b87e7366cebfc16532f
treeae66c67f4c809db08dcec73fa27fe9048286575d
parent7cc0014244124aea59672904de65a979a8e5fb2c
Name and order the memory core code

The names of the memory core that only one of its parts uses start with
that part: the day helpers of the journal, the record decoder of the
tree, the message kinds and check of the log, and the view file of the
memory. The types of the core start with a capital letter: Journal,
Position, Records, Syncer, and NodeKey.

The fake summarizer of the tests is in summarizer_test.go, because most
tests use it. The test helpers of the tree, the log, the syncer, and the
replay test start with their part. The declarations of the core files
follow the order of the go-code skill. The behavior does not change.

Issue: 947bddb
23 files changed:
build_queue.go
build_queue_test.go
clock_test.go
compactor.go
compactor_test.go
journal.go
log.go
log_test.go
memory.go
memory_test.go
model.go
model_test.go
probe.go
probe_test.go
records.go
replay_test.go
summarizer_test.go [new file with mode: 0644]
syncer.go
syncer_test.go
tree.go
tree_test.go
view.go
view_test.go