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
[rector] [dead-code] Remove few ifs that are always true - part #2 #12700
Conversation
9ce62af
to
f0aca03
Compare
Codecov Report
@@ Coverage Diff @@
## 5.x #12700 +/- ##
=========================================
Coverage 58.58% 58.58%
+ Complexity 33610 33607 -3
=========================================
Files 2180 2180
Lines 101733 101730 -3
=========================================
Hits 59597 59597
+ Misses 42136 42133 -3
|
501d9b9
to
ba75ebc
Compare
Ready for review ✔️ |
… type, as strictly defined by new
ba75ebc
to
199152b
Compare
Rebased ✔️ This is good to go now 👍 Basically 2nd part of previous just merged PR :) |
199152b
to
f635008
Compare
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.
The code changes make sense. I dug through the code if the removed if statements won't cause any issues or performance degradation but it all looks like it's handled in lower layers.
Adding the return types to public methods is a BC break but since these changes would go to a major release, we can get it merged. We were forced to add types by our dependencies in multiple places anyway so a couple more shouldn't cause any surprises.
Thank you Tomas! 👍
Younger brother of #12693