Closed const-ae closed 3 years ago
Well, as a general rule, if matrixStats::rowQuantiles
has the arguments, the generic should probably have them too.
I'm talking about arguments that make sense for matrix-like objects in general. Not all arguments fall in that category but it seems that drop
and type
do.
Where do we sit on this?
I rebased the PR on the current master to resolve the merge conflict. I think we can merge this now :)
Thanks, @const-ae!
After some discussion with @LTLA in https://github.com/const-ae/sparseMatrixStats/issues/7, I decided that it is probably a good idea to include
drop
andtype
(whichsparseMatrixStats
now fully supports) in the generic method signature.What do you think?