Skip to content

Removing non_exhaustive can potentially be a breaking change #16417

@ehuss

Description

@ehuss

Per the discussion in https://github.com/rust-lang/reference/pull/1837/changes#r2532838829 and rust-lang/rust#147722, there are some edge cases where removing the #[non_exhaustive] attribute can potentially be a breaking change. That issue has a proposal that could fix that issue, but I wanted to create an issue here just to track this just in case it doesn't get resolved. If it doesn't get resolved, we may want to consider adding something to the SemVer compatibility chapter.

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-semverArea: semver specifications, version matching, etc.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions