OvermindDL1

> I guess another viable option could be to use issues here at github for discussions, just labelling them as such... I'm always good with that, though if real-time is...

> Not sure how to test this? @OvermindDL1 do you have a benchmark that can be run? I do on my web server, shouldn't be hard to plug this in...

I'm getting `'|.' is not a valid value identifier` for note when I'm trying to inspect it's type.

> as you can see, some a bit slower, some a bit faster, but largely in the same ballpark. Hmm, and I have algorithmic changes in mind that could speed...

> I'd like to point out that I'm using Belt functions in the benchmark implementation already because OCaml's default implementations were causing stack overflow errors when e.g. concatenating a list...

> Are u aware ocaml stdlib is not stack safe in native either, some of my benchmarks show that the js lib is almost as fast as native. Is it...

> @OvermindDL1 is this something you're interested into completing? If not I'll close it. @tcoopman As it stands it doesn't have a substantial enough performance benefit to warrant inclusion especially...

> Is ~key:_ supposed to work the same as key in React/Value and keyed in Elm? Nope. The two things of `key` and `uniq` kind of work like keyed in...

From looking at the code though that you posted above, `key` is doing what it should be, it is keying it based on the value you pass in to it...

> Is there an equivalent feature in bs-tea? Actually the same thing will happen in this case as well. The issue you were running in to was changing a part...