Tim
Made some solid progress. Will close this in favour of the other PR.
The types need to be improved to handle Iterable's correctly.
/rebase
> its use with sliding, dropping, and bounded variants Bounded and dropping is an easy fix - only add items to the replay buffer if they are successfully added to...
> Can this be more pronounced? Currently its hard to even notice that there is a change at all. The goal was to make only a small visual difference, but...
> We can expose the most efficient API for each use-case. From a maintainability perspective, I would prefer not to have a replay version of each AtomicPubSub implementation. Also, things...
> my implementaion is more efficient for unbounded type I ran some benchmarks and they are pretty much the same, so I think we should just go with the less...
Android / chrome. I tried the forcing gpu rendering trick, but it didn't have any effect. The difference here is that it was using `backdrop-filter`.
> We emit 10000 elements, but we have 20000 in RAM because we keep the same elements in 2 places. It will just be overhead in terms of the replay...
Here is some videos showing the difference: https://github.com/user-attachments/assets/b9facb34-c411-4bb1-af69-4d0250488379 https://github.com/user-attachments/assets/302af698-019c-467a-a8d1-5446ed066b5b