generics candidates around image/spatial data

[HelenaLC]

Noting down cases we encountered... all open to discussion/suggestions!

• base::data(...)
  • dispatch on ellipsis is problematic
  • SpatialData sets \(x, ...) generic at the moment
• base::scale(x, scale=TRUE, center=TRUE)
  • missing ellipsis/does not allow for other arguments
  • SpatialData sets \(x, ...) generic at the moment
• base::labels(object, ...)
  • SpatialData sets \(x, ...) generic at the moment
  • but \(object, ...) could probably be used instead
• base::sequence(nvec, ...)
  • not sure sure about this one...
  • SpatialData sets \(x, ...) generic at the moment
• base::transform('_data', ...)
  • also S4Vectors::transform('_data', ...)
  • also used by SpatialData
• EBImage::image(x, ...) (generic)
  • perhaps of general interest for its simplicity
  • SpatialData sets \(x, ...) generic at the moment
• EBImage::rotate(x, angle, ...) (function)
  • SpatialData sets \(x, ...) generic at the moment

[hpages]

Thanks Helena. It will take a few days before I can get to this, probably not before Thursday or Friday next week.

[Artur-man]

I agree with @hpages that we should not overdo it, but here are some of the ones I found.

• AnnotationHub::query(x, pattern, ...)
  • breaks SpatialData if loaded.
  • SpatialData sets \(x, ...) generic at the moment
• TBA