Aleksey Khudyakov

> On the other hand, if we decide to give a green light to new instances of Random, we can define instance Random Rational just applying toRational to Doubles in...

I think it's quite clear. Current documentation doesn't describe functions' behavior well and it would be nice to make it more informative (PRs are welcome)! RE unsafe variants. I think...

I think any function which could perform unchecked out of bounds access should be marked as unsafe to make clear that they can violate memory safety. It probably make sense...

If it is internal function it should be given sufficiently scary name or moved into some *.Internal module. Also no one reads all that small print about which function is...

No worries. Still I think that exporting internal and public API from same module is wrong design. It's too easy to confuse then. Moreover same internal APIs contains stream/unstream &...

Another point about public/internal API distinction: #70. Someone asked for API which would be marked internal so it makes sense to make it public.

Their only common point is that they about exposing/not exposing internal API. Otherwise they're largely independent. So it's probably better to discuss them separately. So we have two questions. 1....

This is however very breaking change. Due to design of unboxed vector (which I consider a mistake) this change will break all unboxed vectors. They require defining data instances and...

Sorry, I missed mutually recursive `basicUnsafeIndexM` and `basicUnsafeIndexM#`. I withdraw objection

I tried to measure impact of this optimization. To do so I added simple benchmark which computed variance of vector of doubles (branches `index-profiling` and `index-profiling-B`) in two otherwise identical...