-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Turn compatibility lint match_of_unit_variant_via_paren_dotdot
into a hard error
#36871
Conversation
Started crater run comparing 1d64acd and 982770d01b44490666f475ab5caa7f157ea0dfc8. |
☔ The latest upstream changes (presumably #36814) made this pull request unmergeable. Please resolve the merge conflicts. |
Crater report: https://gist.github.com/nikomatsakis/ac9e9e1abf4cf42c398680ac5afa3a74
|
ring-0.4.3 - |
@bors r+ |
📌 Commit b3cb8f6 has been approved by |
Seems ok. |
Turn compatibility lint `match_of_unit_variant_via_paren_dotdot` into a hard error The lint was introduced 10 months ago and made deny-by-default 7 months ago. In case someone is still using it, #36868 contains a stable replacement. r? @nikomatsakis
Just restarted buildbot, but this passed almost all tests, so merging. |
Partially stabilize RFC 1506 "Clarify relationships between ADTs" Lifted restrictions on tuple structs/variants are stabilized, i.e. `S{..}` can be used with any structs and empty tuple structs are permitted without feature gate. Numeric fields in struct expressions/patterns `S { 0: a, 1: b }` are **NOT** stabilized. This was implemented 1.5 months ago in Rust 1.12, but this is a tiny technical change that could probably go even without RFC/stabilization period. cc rust-lang#35626 rust-lang#36871 r? @nikomatsakis
The lint was introduced 10 months ago and made deny-by-default 7 months ago.
In case someone is still using it, #36868 contains a stable replacement.
r? @nikomatsakis