Skip to content

Rework component_pool chunk storage #219

Open

Description

@kgorking

Use something like a sparse_set to manage the chunk storage. Keep them ordered, without the need to move them around too much (swap-from-last erases ok).

Activity

  1. self-assigned this
    on Oct 4, 2023
  2. changed the title [-]Rework component_pool chunc storage to avoid moves[/-] [+]Rework component_pool chunk storage to avoid moves[/+] on Oct 4, 2023
  3. changed the title [-]Rework component_pool chunk storage to avoid moves[/-] [+]Rework component_pool chunk storage[/+] on Mar 18, 2024
  4. kgorking commented on Mar 18, 2024

    @kgorking
    OwnerAuthor

    Reason:

    • The current implementation was a fun experiment, but it has gotten unwieldy and hard to maintain.

    References:

    Plan:

    • Create a self-contained range tree that can hold ranges and their data
      • Implement as an AA tree
      • Use a compact layout. New data is filled into current holes or appended to the end.
    • Write algo for tree diff/intersection
  5. kgorking commented on Mar 20, 2024

    @kgorking
    OwnerAuthor

    Well nuts to that. Wrote an allocator instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions