Open kvark opened 4 months ago
I see similar errors (e.g. https://github.com/dimforge/rapier/issues/586) are reported recently not only in this repo.
I found this error was relaxed only since Rust 1.74.0. This change:
Replace private_in_public lint with private_interfaces and private_bounds per RFC 2145. Read more in RFC 2145.
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. For Rapier3d, it's not about semver at all. Let me edit the title accordingly.
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: