-
Notifications
You must be signed in to change notification settings - Fork 81
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
Port plVaultClientApi to standard C++ containers #1468
Conversation
The owner and seen info was never used here. It's not even clear what they would refer to, because every node appears exactly once in s_nodes, regardless of how many refs it has.
As with s_nodes, the owner and seen info was never used here. The fields were never filled in either, even though here it's clear which values they should have.
I wonder... considering that all |
I think that would be ideal (in another PR), but we'd want to make sure that |
1fb140d
to
b760a54
Compare
Here I go, touching more important and complex code - what could go wrong?
More seriously, this makes the vault logic a bit more readable and less complex, because it eliminates some manual memory management and wrapper structs. Some of the code is still quite verbose though, because of how the C++ map API is designed.
This eliminates the last use of the weird custom intrusive hash table pnUtHash (aka
HASHTABLEDECL
/HASHLINK
).