rescript-vector is a persistent vector data structure that can be used in ReScript.
Persistent
Any function that changes the vector returns a new instance of it while not modifying the original vector. Just like any strings or numbers, vectors are treated as never-changing values.
Vector
Similar to Array, but vectors can be dynamically increased or decreased in size. (in this sense, JS arrays are better called vectors) Elements can be added or deleted to the end of the vector, and you can access them in constant time.
ReScript's standard library Belt has persistent data structures like Array and List, which are mature and complete.
However, Belt.Array does not have push/pop functions like Js.Array2 does. This is because pushing/popping while maintaining the persistency cost a lot. Specifically, it takes O(n) time and space complexity.
Belt.List can add or delete elements in O(1), but its access time is O(n) which could cause another latent performance issue.
rescript-vector do push/pop in amortized O(1) and O(log n) at worst. Accessing an element takes O(log n) time complexity. 1
While gaining persistency, this is also a good trade-off in most cases.
Inside the vector, there is a very specially implemented trie, a bit-partitioned vector trie. You can find more detailed explanation here.
Yes, there exists prior JavaScript implementations for persistent vector. The most famous ones are Immutable.js and mori. 2
Though they are great in many ways, the biggest problem is that their interfaces do not match Belt. So we either have to give up zero-cost binding or ergonimics. Moreover, they are both designed for heterogeneous vectors, a considerable overhead is inevitable.
Last but not least, as a fanatic ReScript user, I had to rewrite it in 100% ReScript.
In the process of implementing persistent vector, some optimizations found could further improve performance compared to other libraries.
As a result, many operations are much faster, especially Array conversion, making rescript-vector more tolerable in practice.
See benchmarks.
MIT