Skip to content

See if non_exhaustive would be useful for 1.0 #4080

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.

Sign up for GitHub

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

Jump to bottom
Open
tgross35 opened this issue Nov 17, 2024 · 0 comments
Open

See if non_exhaustive would be useful for 1.0 #4080

tgross35 opened this issue Nov 17, 2024 · 0 comments
Labels
S-waiting-on-decision
Milestone
1.0

Comments

@tgross35
Copy link
Contributor

There are a handful of structs that users should be able to access but possibly not construct in case fields change in the future. Currently we often do this by having a single private field, but maybe #[non_exhaustive] would be better suited here.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
S-waiting-on-decision
Projects
None yet
Milestone
1.0
Development

No branches or pull requests
1 participant
@tgross35