Ripped out inlined (in-RAM) btree union

Browse Source

This did not turn out to be useful, mainly because type-agnostic
inlining requires unnecessary encoding/decoding and risks a higher RAM
allocation than is really needed. It's better to just reserve a bit in
the weight field and allow higher-level operations to use
operation-specific unions.

            code          stack

  before:  31580           2072
  after:   31160 (-1.3%)   2072 (+0.0%)

...

This commit is contained in:

Christopher Haster

2023-11-08 01:31:52 -06:00

parent d36d67c9b0

commit f9a38756ca

3 changed files with 446 additions and 596 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

+381 -331

File diff suppressed because it is too large Load Diff