ripytide

So I think there are two main use-cases in play here: - Users wanting to rotate/flip an image in their code. - Codec authors needing to rotate/flip images as part...

Oh I've just found the #793 issue, that would have saved me some typing regarding the crate splitting :smile:

In #2243 you mentioned not making breaking changes to the main branch in case patch releases are needed, but leaving them as open PRs risks merge conflicts. How about we...

> The dynamic of having a contributor say "let's do X!" and then expecting the maintainers to figure out what impact the change would have on downstream users, future compatibility,...

> You don't have to be the one to write-up a detailed analysis of how the switch would work, and what the pro and cons would be. However, somebody would...

Some utility functions were used in both normal tests and protests so I found it easier to just leave them together, but I suppose the best solution would be to...

Okay I've extracted all proptests into their own `proptest` modules which is definitely much nicer. Thanks @cospectrum for the pointer on making testing utilities `pub`.

>An external type might incidentally implement Deref but surely it doesn't Deref and can then only be used in the former case with the current design Ah ok, I think...

The main information I was thinking about was color-space information. Perhaps `ColorSpaceInfo` would be a better name so as not to be confused with `.jpg` metadata such as GPS information....

I suppose the alternative to using a type-map like `Extensions` for `ImageMetadata` would be a strongly-typed struct like this: ```rust struct ImageMetadata { color_space_info: Option, original_file_size: Option, original_image_dimensions: Option, loop_count:...