Minor optimizations in if() blocks #2951
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A PR with a few micro-optimizations for performance and readability.
if()
expression orderExpressions in
if()
are run left-to-right, and evaluating computationally smaller expressions can improve the performance a little bit. This PR contains two of such improvements where it puts=== null
call and a truthy evaluation ahead of function calls.if()
-elseif()
-else
branching optimizations.If such a block
return
s something, the execution of that function is complete, so we often do not needelseif
orelse
blocks. While they don't provide any performance benefit, we take nested code outside, which reduces the cognitive load on developers.