Why does DynamicImage::filter3x3() take &[f32], rather than &[f32; 9]?

[LikeLakers2]

Hi! I was browsing image's documentation, when I noticed the point mentioned in the discussion title.

To give more info: DynamicImage::filter3x3() takes an &[f32], but requires the slice's length to be 9 - otherwise it panics at runtime.

Wouldn't it be better to have the kernel parameter be an &[f32; 9]? This would ensure that any problem with a slice's length would be caught at compile-time.

If this change is desired, I can put together a quick PR for this change.

[197g]

The answer is probably that this exact API has been unchanged since at least 0.5 which predates convert::TryInto/TryFrom by a lot. That's required to make the array type actually usable. As for PR, yes, I do agree it would be better and would gladly take a PR. That said, but it's a major breaking change and going to go into the next major version.

[LikeLakers2]

Sure, I'll go ahead and make the PR then.