Skip to content
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.

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

Add enum_non_exhaustive_tuple_variant_changed_kind lint. #1215

Conversation

shreyans413
Copy link
Contributor

Addresses the following checkbox in #884 -
public API #[non_exhaustive] tuple variant that has at least one public API field changes to another kind

@obi1kenobi obi1kenobi enabled auto-merge (squash) March 25, 2025 02:29
auto-merge was automatically disabled March 25, 2025 04:22

Head branch was pushed to by a user without write access

@shreyans413 shreyans413 force-pushed the enum_non_exhaustive_tuple_variant_changed_kind branch from a933518 to e0d6765 Compare March 25, 2025 04:22
@shreyans413 shreyans413 requested a review from obi1kenobi March 25, 2025 21:03
@obi1kenobi
Copy link
Owner

This has merge conflicts at the moment btw.

@shreyans413
Copy link
Contributor Author

This has merge conflicts at the moment btw.

I need to update the snapshots due to the new lints, on it!

@shreyans413 shreyans413 force-pushed the enum_non_exhaustive_tuple_variant_changed_kind branch from 3867a7f to 7b7e44f Compare March 26, 2025 00:44
@obi1kenobi obi1kenobi enabled auto-merge (squash) March 26, 2025 00:56
auto-merge was automatically disabled March 26, 2025 00:58

Head branch was pushed to by a user without write access

@shreyans413 shreyans413 force-pushed the enum_non_exhaustive_tuple_variant_changed_kind branch from 378b85c to f849045 Compare March 26, 2025 00:58
@obi1kenobi obi1kenobi enabled auto-merge (squash) March 26, 2025 00:59
@obi1kenobi obi1kenobi merged commit 2b52031 into obi1kenobi:main Mar 26, 2025
31 of 32 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants