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

Specify behaviour when dealing with duplicate keys #12

Open
mattnathan opened this issue Feb 3, 2022 · 0 comments
Open

Specify behaviour when dealing with duplicate keys #12

mattnathan opened this issue Feb 3, 2022 · 0 comments

Comments

@mattnathan
Copy link

I've been trying to find what the behaviour of different methods is with respect to duplicate keys, but can't find anything official or obvious.

Some limited testing has shown that duplicates are added to the list rather than replacing existing entries, but without it written into the specification I'm not sure whether I can rely on this or not. I've also noticed that Finding using a key that is duplicated seems to return the SkipListElement at the start of the duplicated block (so you can call Next to get the next, etc), again not sure I can rely on this behaviour or not.

For the record, I'd like duplicates to continue to be added.

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

No branches or pull requests

1 participant