ripytide

Two approaches I can think of: 1. Put all rotation, flipping, overlaying, cropping and tiling functions all in one module called something like `compose` 2. Put rotation functions in a...

Ditto https://github.com/image-rs/imageproc/pull/660#issuecomment-2134034460 I think the gradient one liner functions are poor for readability and maintainability and should be deprecated.

I'd disagree with renaming `filter_clamped` to `filter` since shorter names are not always better names for code readability as the name `filter` hides that it clamps pixel sums unless you...

Not to mention that all the gradient functions all currently only support `GrayImage`, and not color images. Supporting any image pixel would require repeating `filter_clamped()`'s trait bounds on every one...

I've just finished a personal project of mine and so find myself with an excess of coding time and motivation. I have minor plans to use some some sort of...

It seems we need to bump the minimal rust version now since one of our dependencies, I think `bitstream-io` now requires `v1.79`

Looks like no impact: Before PR: ``` test contrast::benches::bench_stretch_contrast ... bench: 660.08 ns/iter (+/- 2.24) test contrast::benches::bench_stretch_contrast_mut ... bench: 0.25 ns/iter (+/- 0.00) ``` After PR: ``` test contrast::benches::bench_stretch_contrast ......

Have you seen the `_mut()` variants of many of the functions in the crate since they don't allocate as they take `&mut Image` argument? (Maybe not in the latest published...

See #622 where I had similar thoughts. There are a few tradeoffs involved in the current method but the new doc macro has helped somewhat in preventing duplicated doc-comments and...

I think that could work, but some downsides I can think of might be: - What about methods like `replace` which takes two images, would that require another trait or...