Open rayegun opened 7 months ago
That would be useful. I'll consider it for CHOLMOD 5.2 (I would bump the 2nd digit from 1 to 2, because this would be a new addition to the user-visible API). I'd like to keep CHOLMOD 5.1.1 as-is for SuiteSparse 7.5.0.
Currently the semantics of
cholmod_*_xtype
are not great since it mutates the data type of an object. It would be nicer in most cases to havecholmod_*_copy_xtype
which returns a new object with the new data type. This would avoid the double memory allocation ofcholmod_*_copy
followed bycholmod_*_xtype
.