Vincent Barrielle

That's because I'm planning to add block compressed (BSC/BSR) matrices later, and I was planning to name them BsMat. However it could be nice to have them as bs::Mat under...

> After trying out the library for a bit, I've found some places in the API that are a bit painful to work with at the moment. Number one is...

FYI I've started splitting this issue into multiple single issues to better track progress. I'll link the issues here.

> Another more basic set of things that is missing is more operations on elements of matrices/vectors. E.g. retrieving and setting a value at a particular position just like a...

> Speaking of views, it would be very nice to have views that are arbitrary sub-regions of the matrix/vector, as well as regions that extend past the boundaries of the...

> One set of very useful things that is missing is support for per-element operations between matrices/vectors. For example if I want to multiply one vector by a constant and...

> It would be very nice to be able to construct a sparse array from a Vec, for example, or dot product a sparse vector with a Vec. See issue...

Glad to hear it! Meanwhile, I've started [binding the CAMD part of suitesparse](https://github.com/vbarrielle/sprs/tree/bind_suitesparse_camd), and I'll probably do AMD next, so this should be nice to compare!

Hello and thanks for this report. It was indeed a design choice that the basic constructor for `CsMat` would not do too much magic. Looks like the proper choice would...

> Looks like the proper choice would be to add a constructor that is able to produce this summation of repeated indices and sorting of indices. > > Even a...