Skip to content

Come up with a proper system to store per-object information #21

Description

@sin-ack

After the object rewrite there's still one part that sucks: The storage of tiny object-related bits on each object's type. Right now this is admittedly a mess. We have a couple viable approaches here:

  1. Screw space optimization, give each object/map type its own heap word to put its bits into: This wastes 63x space for things like method maps.
  2. Incrementally slice a well-known part of the object header: We can run out of header space easily. Also, I believe I've hit various Zig packed struct bugs while doing this with ExecutableMap.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions