Aleksey Khudyakov

TH should be avoided for another reason as well. It's broken for cross-compiling and effectively it means that nothing could be cross-compiled

At this point we have working doctests but not all functions have examples so PRs with more are welcom

This is very tricky function to write inside stream fusion framework. `b` is hidden inside existential state of stream and we don't have any way to access it: ```haskell data...

There's consensus that such function is useful. Although it could be only implemented without fusion support. I'm mrking it as help wanted

`unstreamPrimM` _is_ more performant and _is_ unsafe. Unsafety alone should not stop us. We have full complement of unsafe functions in the name of performance. What's crucial is to understand...

Out of curiosity I tested what will happen if one to remove all `INLINE`. Compilation time went 91s → 34s. And benchmarks suffered 150-200× slowdown. After all in order to...

RE: name clashes. Only way to avoid them is to add prefixes for all mutable versions. Also there's precedent for name clashes: init, tail, drop, replicate etc clash already. RE:...

I'd like to propose following naming conventions. 1. Functions that don't change vector's elements (like folds) or functions that create new vector (replicate/generate) get same name as pure counterpart. 2....

I've added PR with what I think uncontroversial additions. Now there's question whether right folds should be included. We can't use laziness to abort computation early and have to read...

My 2c Working with unboxed data in haskell is somewhat awkward and require some sort of boilerplate no matter what. With Storable one has write boilerplate instance as well. And...