You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The new version(s) of opencv-rs make a fundamental change and add a BoxedRef return type to capture the lifetimes of the underlying Mat data. These new return values result in errors for some conversions within the crate when updating via the instructions in the readme.
This crate is super helpful and an update would be very much appreciated.
Additionally, do you have any comments on the future of the crate? Can we expect routine updates, or is it more-or-less abandoned.
If the latter, we will (sadly) look into other options for our codebase.
The text was updated successfully, but these errors were encountered:
I think the fix might be as simple as adding a try_clone()? to the end of each line that makes a Mat from a slice. This will make an explicit copy of the slice and return a new Mat proper with the (now owned) data (vs. a BoxedRef<Mat>). It makes a deep copy, but I believe this is the intended/expected behavior of the crate in general anyway?
The new version(s) of
opencv-rs
make a fundamental change and add aBoxedRef
return type to capture the lifetimes of the underlyingMat
data. These new return values result in errors for some conversions within the crate when updating via the instructions in the readme.This crate is super helpful and an update would be very much appreciated.
Additionally, do you have any comments on the future of the crate? Can we expect routine updates, or is it more-or-less abandoned.
If the latter, we will (sadly) look into other options for our codebase.
The text was updated successfully, but these errors were encountered: