-
Notifications
You must be signed in to change notification settings - Fork 52
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
Patterns of empty types #115
Comments
This issue is intended for status updates only. For general questions or comments, please contact the owner(s) directly. |
Here's the status we're at today, at the start of the goal period:
|
Update since last time:
Next steps:
|
Update since last time:
Next steps:
|
Update since last time:
Next steps:
|
No progress since last time. |
Summary of the progress over the semester: I went at my own pace which is a slow pace. I wrote and posted the never patterns RFC as an attempt to make progress without figuring out the whole picture, and the general feedback was "we want to see the whole picture". Next step will be to write up an RFC that includes a clear proposal for which empty patterns can and cannot be omitted. This is 100% bottlenecked on my own writing bandwidth (reach out if you want to do this together!). I did not end up making much use of the project goal structure, so I decided not to renew this goal for 2025H1. I will keep working on it at my own pace. Stay tuned for future developments! |
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: