I was messing around with State in the fem branch this morning, trying to remove the need to keep a shared_ptr internally to store a pointer to T. I was able to do that using explicit move semantics, but that caused some interesting - although repairable - problems with the parts of the class that uses pointers.
I think I have some ideas on how to remove pointers from the API and still use them internally. Pointers are only there for the purpose of connecting to C-based solvers. I think I can internalize this with link() and unlink() operations that do some pointer trickery without exposing the pointers on the API.
I was messing around with State in the fem branch this morning, trying to remove the need to keep a shared_ptr internally to store a pointer to T. I was able to do that using explicit move semantics, but that caused some interesting - although repairable - problems with the parts of the class that uses pointers.
I think I have some ideas on how to remove pointers from the API and still use them internally. Pointers are only there for the purpose of connecting to C-based solvers. I think I can internalize this with link() and unlink() operations that do some pointer trickery without exposing the pointers on the API.