👍 Agree in principle, yes, this should be gone. If we de-emphasize use of the type system for describing the image, the trait should naturally play a diminished role in future designs anyways. It does not sufficiently generalize operations we want in any case.

As for mitigations: The role of Dynamic* image is that its variants are all convertible in some sense. I wonder if we could provide an explicit as_image::<P: Pixel>() -> TBD<P> adapter which implements the trait variant that the caller chooses. This doesn't resolve the inherent problem we have with the Pixel type itself but resolves that we need to choose one. Just an idea, I'd want to move this PR forward regardless of the evaluation of that idea.

@fintelia Should we just decide to do the cut-off for the next major version now by

• a 0.25.3 release
• moving 0.25 into a version branch (not promising any more releases, but who knows)
• declaring main to be development by marking its version as 0.26-alpha?

It seems like a good time to get rid of old cruft.