I don't have a good feel for the overhead of
std::shared_ptr
I mean a shared_ptr of grid is not a container of grids
in particular, this was in the context of the sparse-direct solver data structures, which are kind of a mess
I am starting to experiment with introducing
std::unique_ptr and to avoid raw pointers unless they are "observing" pointers with no memory management
I think the combination of
std::unique_ptr and properly documented raw, observing pointers will be a significant improvement
Sounds like a case for a move ctor from what your describing
You have a thing that gets made and it's lifetime needs to be given to something else
I try to avoid all smart pointers
And it sounds like promoting your grid to an xvalue if possible and handing it to your distmatrix would do the trick
maintain an
std::vector of them where? and on which processes?
Or whatever is supposed to hold the lifetime of the grids
Based on your last sentence it sounds like a distributed data structure has a member which represents multiple grids
I would still use move semantics to move generated grids into that vector
what is your aversion to
std::unique_ptr?
I can review but it would require Waiting until Jan 1
the improvement in the interface is substantial enough that it will be worth merging once the dust settles (probably in several more days)
also, I am bundling in a Mathematical Programming Software (MPS) reader in the sparse-direct changeset
easily checking that one gets the same results as http://www.netlib.org/lp/data/minos is useful
it just isn't documented yet I think
it is heavily used within Elemental's Interior Point Methods