persistent-hash-trie
persistent-hash-trie copied to clipboard
Pure string:val storage, using structural sharing
I know this project is not active, but I was [benchmarking JS hashtrie implementations](https://github.com/mattbierner/js-hashtrie-benchmark) and I think `dissoc` has a bug: ``` var p = require('persistent-hash-trie'); var h = p.Trie();...
According to immutable's tests on reduce-based object iteration, ie10 (and possibly others) are failing due to growing stack space: Acceptance: - Stack size usage for reduce should be constant size....
At the moment, the benchmarks show it far too close to persistent-hash-trie implementations. I'd expect that shallow-clone would be _WAYYYY_ slower. ``` bash assoc property with Trie of 1 //-------------------------//...
As a user, I don't want speed to be impacted adversely by constantly re-hashing the same keys. Acceptance: - explore options and impact of memoizing the internally used hash function.
Change the Trie to use Array-Mapping to store keys, as set out in Bagwell (2001) - Ideal Hash Tries.. Measure performance to determine efficacy.
As a user, I want to be able to use immutable-hash-trie in any semi-common environment, including: - ie 6+ - chrome 4+ - FF 3+ - opera 10+ - safari...