Reversed LFSR_ATTR id/tag argument order

Browse Source

I've been wanting to make this change for a while now (tag,id => id,tag).
The id,tag order matches the common lexicographic order used for sorting
tuples. Sorting tag,id tuples by their id first is less common.

The reason for this order in the codebase is because all attrs on disk
start with their tag first, since its decoding determines the purpose of
the id field (keep in mind this includes other non-tree tags such as
crcs, alts, etc). But with the move to storing weights instead of tags
on disk, this gives us a clear point to switch from tag,w to id,tag
ordering.

I may be thinking to much about this, but it does affect a significant
amount of the codebase.

...

This commit is contained in:

Christopher Haster

2023-04-07 13:03:03 -05:00

parent a463d6f106

commit 7eb0c4763a

5 changed files with 2534 additions and 2535 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

tests/test_btree.toml

+133 -133

File diff suppressed because it is too large Load Diff

tests/test_rbyd.toml

+2245 -2245

File diff suppressed because it is too large Load Diff