Tracking Issue for Bevy special-casing of implied bounds and -Zno-implied-bounds-compat
#119956
Labels
C-tracking-issue
Category: A tracking issue for an RFC or an unstable feature.
P-high
High priority
T-types
Relevant to the types team, which will review and decide on the PR/issue.
Comments
jackh726
added
C-tracking-issue
jackh726
changed the title
lcnr
changed the title
-Zno-implied-bounds-compat
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Jan 18, 2024
error on incorrect implied bounds in wfcheck except for Bevy dependents Rebase of rust-lang#109763 Additionally, special cases Bevy `ParamSet` types to not trigger the lint. This is tracked in rust-lang#119956. Fixes rust-lang#109628
This was referenced Jan 19, 2024
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Jan 19, 2024
use implied bounds compat mode in MIR borrowck cc - rust-lang#119956 - rust-lang#118553 This should hopefully fix bevy 🤔 `cargo test` ends up freezing my computer though, cargo build went from err to ok however 😁 r? `@jackh726`
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Jan 19, 2024
use implied bounds compat mode in MIR borrowck cc - rust-lang#119956 - rust-lang#118553 This should hopefully fix bevy 🤔 `cargo test` ends up freezing my computer though, cargo build went from err to ok however 😁 r? `@jackh726`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In #118553 we're adding special casing for functions containing a type using
ParamSetfrom Bevy to not emit an error or warning for incorrect implied bounds (see #109628). This special casing can be disabled via the unstable-Zno-implied-bounds-compatflag.The expectation is that we may be adding additional implied bounds that (with some modifications to Bevy) allows Bevy's dependents to continue compiling without errors or warnings. When those changes are made, we want to remove this special casing. Alternatively, if we find out we can't add additional implied bounds in a way that allows dependents to continue compiling, we still want to remove the special casing.
The text was updated successfully, but these errors were encountered: