Aurelia Molzer

I' considering closing this due to the above problem. If we do lock-step then we haven't actually solved the issue, depending on `image` with default-features = false seems almost as...

Alright, I'm closing this. As a short summary: While we want better shared low-level buffers we probably won't get to those by extracting the `image` structs (other requirements, have not...

As a note, I'd very much appreciate seeing `wasm32-wasip1` or `wasm32-wasip2` targets tested anyways. So if we can make that the 32-bit test configuration we get two birds with one...

Some pointers: 1. Install wasmtime 2. ``` # .cargo/config [target.wasm32-wasip1] runner = ["wasmtime", "--dir", ".::"] ``` 3. Remove `term` from the dev-dependency tree, it's just for one example. It seems...

Alternative fix for this calculation is up at: #606 By no longer multiplying by `8` outside of `u64` values we bound all indices to the length of the image buffer,...

This was superseeded by #606, thank you for the test case sketch..

:+1: 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...

@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...

[`ImageBuffer::apply_orientation`](https://docs.rs/image/latest/image/enum.DynamicImage.html#method.apply_orientation) addresses these in-place edits. Arbitrary affine operations are of course not supported here, just combinations of mirrorring operations.

Given the dominant prior art (or posterior art?) of other formats choosing that triple for color space representations, yes, certainly. Should be simple to add? Similar to `icc`/`gama`/`chrm` it'd be...