-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Exhaustive case near and far #9656
Exhaustive case near and far #9656
Conversation
I was thinking about opening another PR just for dropping |
e2a27a7
to
1767b62
Compare
Bump 🏓 |
Ping /cc @asterite @bcardiff @straight-shoota |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great, thank you!
Second approval any1? /cc @bcardiff @straight-shoota @waj @jhass |
Yo, could this be merged or sth? |
It needs a second review. |
@asterite so when this will happen? |
I don't know. But it doesn't matter, because until 1.0 is released whether this PR is merged or not doesn't change anything. In fact, even after it's merged it dosent produce visible changes. |
@asterite That's the point, this PR doesn't bring any substantial changes so why does it takes almost 2 months already to get it through? |
1767b62
to
906ef37
Compare
Is there anything holding this back? /cc @straight-shoota @jhass @bcardiff @waj |
This PR aims to be a small followup to #8424, it:
case
statements in few places throughout the stdlibelse # go on / ignore / nothing to do
branchesLog::Severity::Warning