You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the generics are a mix of implicit and explicit and are inconsistent in terms of how they are exported and documented. Would be good to clean this up.
Taking inspiration from Bioconductor I think we should define explicit generics rather than being reliant on the implicitly generated ones. In particular for things like as.data.frame care is needed on which arguments should be exposed for multiple dispatch (again taking Bioconductor as an example)
The text was updated successfully, but these errors were encountered:
This is also connected to #177 . My current thinking is we should implement these as S3 generics (to avoid these collisions and inconsistencies) that in turn dispatch to the as method to handle the actual s4 conversions.
Currently the generics are a mix of implicit and explicit and are inconsistent in terms of how they are exported and documented. Would be good to clean this up.
Taking inspiration from Bioconductor I think we should define explicit generics rather than being reliant on the implicitly generated ones. In particular for things like
as.data.frame
care is needed on which arguments should be exposed for multiple dispatch (again taking Bioconductor as an example)The text was updated successfully, but these errors were encountered: