Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Element List/Map #32

Open
georgefst opened this issue Aug 11, 2021 · 0 comments
Open

Element List/Map #32

georgefst opened this issue Aug 11, 2021 · 0 comments

Comments

@georgefst
Copy link
Owner

georgefst commented Aug 11, 2021

In 87a9283 removing and updating elements went back to being O(n). What we need is a data structure that gives us efficient lookups and allows us to iterate through all elements in the order they were added. I can't immediately see how this would be done without either O(n) deletions or memory leaks, but apparently Python's default dictionaries manage it. Of course, that data structure needs to be implemented in Haskell and Elm, with working serialisation...

In practice, the layouts might always be small enough that this isn't really an issue.

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

No branches or pull requests

1 participant