Aurelia Molzer

If the Limits are an issue for ICC and EXIF I would propose that we (add an option / switch) to count their memory use towards the usual image data...

Should we make a project for planning for `0.24`? Have you tried the Github feature already?

(*Note: moved from a discussion on [an alternative container that should implement the trait](https://github.com/image-rs/canvas/issues/15)) I'm no longer sure if the trait is the correct public interface. We've already had plenty...

> One of the key differences between the two traits is that ContiguousImage defines the exact memory layout of the image data. Imposing *specific* invariants on some data is what...

The following is wrong with wanting to provide a *safe* trait that tries to enforce a particular layout of image data: ```rust // No guarantee that this corresponds to `ColorType`...

> Wouldn't this design require a method call on every use of AsPixels? It would be like the relationship of `Extend` and `IntoIterator`, a trait to normalize the representation to...

> This would be very unpleasant for writing any downstream generic code. Essentially any operation on a dynamic image would be a match with separate branches for each possibility. This...

> What about something like this then? [..] This makes `ContiguousImage` quite like `AsDynamicViewMut` and that might complement the basic implementation on `DynamicViewMut` quite well. The only problem might be...

> But why even bother with implementations in other places? It feels very much as if `std` adding a trait to implement a method on slices... Implementing the exact same...

> We have to make these decisions at some point. In particular it isn't really possible to write generic code without this. In fact, some of the existing algorithm implementations...