Morgane55440
Morgane55440
i'm interesting in working on this. would it be ok for me to do so ? i could probably make a pull request today or tomorrow
after looking at the code, it appears obvious to me that the only code that requires change is that of `distance_transform_impl`. that doesn't seem to hard the way i would...
here is my replacement proposition : ```rust pub enum Norm { /// Defines d((x1, y1), (x2, y2)) to be abs(x1 - x2) + abs(y1 - y2). /// Also known as...
thnk you for the square root, i will add tests and maybe add on documentation for user-facing functions which use the `Norm` Enum before making a pull request. on the...
by the way, i tested and it seems that `as u8` takes the floor. issue is, what we usually need in morphology is the elements which are 'n or less'...
considering we are using `u8` and not `NonZeroU8`, i elected to add tests for `0` for all norms, for erode and dilate. also, due to the fact that `L2` behaves...
as Github so helpfully pointed out, i have made a pull request
> It’s a neat idea - I’d be curious as to what difference benchmarks show between the const bool and the runtime if statements. if there is any it's probably...
very similar issue, don't know if anything has been done about it in the last year and 1/2. more specifically from my experience, entities not included in the vanilla gpose...
seems this is related to #1091 , in particular > Sprinkled a bunch of unsafe impl Send and unsafe impl Sync on top of all IO implementations and inner structures...