You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't want to change the way keys are stored and accessed right now. The implementation is simple and adding a key is an O(1) operation (ignoring a possible reallocation). If you need a hash table with O(1) access time then using parson is not the right choice. You can parse an object using parson and then put all key/value pairs into an actual hash table.
So what I wrote 5 years ago is incorrect. Adding a key is O(n) because it first checks if given key already exists (linear search). I'm currently working on using hash tables in json objects.
No description provided.
The text was updated successfully, but these errors were encountered: