New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build breakage with 0.18 in SolverConstraintsSet
#592
Comments
I see similar errors (e.g. #586) are reported recently not only in this repo. I found this error was relaxed only since Rust 1.74.0. This change:
Since rapier doesn't have a policy about MSRV (right?), technically, this might not be what is considered as a semver breakage. But, I personally feel Rust 1.74 is a bit too strict requirement for a non-experimental library. |
@kvark I’m not sure I understand what semver breakage means here. Rapier got bumped from 0.17 to 0.18 here, isn’t hat what semvers dictates in case of breaking change (apparently including, in this case, a MSRV change)? |
Sorry about the confusion! I was reporting other similar issues to other repos, and they were actually semver-related. |
SolverConstraintsSet
SolverConstraintsSet
I strongly recommend exposing MSRV and having your CI build/run with it specifically instead of the latest stable version. |
Building with Rust-1.73:
My Cargo lock entry:
The text was updated successfully, but these errors were encountered: