Skip to content

Tracking Issue for Bevy special-casing of implied bounds and -Zno-implied-bounds-compat #119956

Open
@jackh726

Description

@jackh726

In #118553 we're adding special casing for functions containing a type using ParamSet from 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-compat flag.

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCP-highHigh priorityT-typesRelevant to the types team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions