You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My proposal for never patterns got sufficient approval to enable experimentation. The unstable feature is now in a usable state, though not complete;
I have an RFC draft for never patterns lying around. It needs to be fleshed out and updated in light of min_exhaustive_patterns being stabilized, after which we can start the RFC process.
The stabilization caused issues because we went from requiring some match arms to warning against them. There was some discussion on the topic, and it was decided to revert the linting behavior for now and find a solution that has a smoother transition.
Next steps:
Backport the approved linting change to beta;
Implement whatever linting mitigation we end up deciding on;
Summary
Introduce an RFC for never patterns or other solutions for patterns involving uninhabited types.
Tasks and status
min_exhaustive_patterns
(@Nadrieril)exhaustive_patterns
to only apply to the case of empty types behind references (@Nadrieril)exhaustive_patterns
(lang )The text was updated successfully, but these errors were encountered: