-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base::cbind()
#116
Comments
Not too surprising. I wouldn't really expect many things to work properly on S4 objects without having at least one package attached, which is the package where these objects are defined/implemented.
Well, that's how things work in the S4 world.
Unfortunately, the solution to your problem is to simply make sure that the DelayedArray package is attached before you start operating on DelayedArray objects or derivatives. BTW how did you end up with HDF5Matrix object
Also
Hope this helps, H. |
Although it's maybe not a traditional S4 generic, the help for I typically dislike and avoid attaching packages at all because of all of the problems it causes. In this case my solution was to just use |
True, I forgot about that. And IIRC we tried to work directly with I'm looking at the commit history for BiocGenerics and it turns out that |
When
x
is anHDF5Matrix
, but I haven't attached any BioC packages, I get:Seemingly, this is because
DelayedArray
only implementsBiocGenerics::cbind
and notbase::cbind
(no idea how that's even possible though), so calling it directly does work:BiocGenerics::cbind(x, x)
.library(DelayedArray)
, which is the more typical way to use this, also works because it overridesbase::cbind
withBiocGenerics::cbind
.Is there any reason why
base::cbind()
isn't implemented?The text was updated successfully, but these errors were encountered: