-
-
Notifications
You must be signed in to change notification settings - Fork 5.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
fix(PVS/V583): The '?:' operator always returns one and the same value #17790
Conversation
@famiu Mind taking a look? |
As you guessed, it is in fact to make it possible to change the value of |
I don't mind it really, I'm just not sure if the most "correct" solution would be to remove the ternary operator (like how it is currently) or just add an ignore directive/comment on those lines. I'll ask an unrelated third party on their opinion. Thanks for your input :) |
My unrelated third-party opinion is that I agree with these changes. If and when the day comes that we want to change |
Since neovim#17790 being merged means we can assume the value of `STATUS_HEIGHT` to always be 1, this commit removes code that's unnecessary if `STATUS_HEIGHT` is 1.
Since neovim#17790 being merged means we can assume the value of `STATUS_HEIGHT` to always be 1, this commit removes code that's unnecessary if `STATUS_HEIGHT` is 1.
Since #17790 being merged means we can assume the value of `STATUS_HEIGHT` to always be 1, this commit removes code that's unnecessary if `STATUS_HEIGHT` is 1.
Since neovim#17790 being merged means we can assume the value of `STATUS_HEIGHT` to always be 1, this commit removes code that's unnecessary if `STATUS_HEIGHT` is 1.
Not entirely sure if this is the correct fix, because the code itself
would make sense if STATUS_HEIGHT had another value. Is it to make it
possible to change the value of it in the future perhaps?