Aleksey Khudyakov

@lehins Yes I moved some safe functions to `Unsafe` module. I found that when all function which work on vector representation directly and not via `Vector/MVector` type classes are defined...

It turns that export of `Vector(Vector)` does not pick pattern defined in module, it packs imported constructor instead. But when module export synonym exporting `Mvector(MVector)` works fine. It seems only...

> I do not agree with this at all. This will make people wrongfully believe that those functions are unsafe. And I can certainly see harm in it! So we...

OK step 1 is done. It turns out that supporting both qualified imports and import `MVector(..)`/`MVector(MVector)` requires quite a bit of jumping through flaming hoops These patterns are used to...

@lehins could you take a look at latest changes? In the end ensuring proper backward compatibility turned out to be quite ugly (but necessary).

Fields accessors also double as documentation. Adding them was right. I'll check that every public vector type except unboxed vectors have them. @lehins thank you for reviews. They're most useful...

So in short stack script cannot work with public sublibraries. Only possible workaround is to split sublibrary into separate package. GHC will probably take quite some time sorting out things...