Closed ripytide closed 6 months ago
I’m a bit ambivalent about this one - it’s nice to save the typing and having to constantly specify the Container type parameter everywhere, but it’s a shame to hide the true type name and require developers to go and learn that this is actually ImageBuffer after all.
Given that we already have the type alias I guess it’s better to use it consistently than inconsistently. (Although I’m tempted to just delete the alias entirely at some point.)
This PR replaces the
ImageBuffer
type with more relevantImage
andGrayImage
types as appropriate.A lot of the time functions return
Image<P>
anyway so usingImage
inside the function makes more sense to me. Also a lot of the timeImageBuffer<P, Vec<P>>
is used explicitly which is repetitive and noisy compared to simplyImage<P>
.The only exception to this is doc-examples which I avoided since it may teach users to rely on the
imageproc::definitions::Image
type synonym which I wasn't sure about. However, I'd be happy to also switch these to useImage
as well if you think that'd be ok.