Skip to content

Better implementation for SeekTable #18

Description

@AaronLenoir

The seektable uses a weird way of handling the fact that multiple placeholder seekpoints can be added. It doesn't store them at the end of the list but just keeps a counter of how many there are. It works, but it's kind of weird.

The better solution is to use a sorted list that can handle duplicate keys. If such a thing exists.

(Actually, I assume implementing a Genereic Collection that always sorts would be kind of OK)

Activity

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

Metadata

Metadata

Assignees

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions