Optimize ActiveSupport::NumericWithFormat#to_s #41801
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.
case format when nil
is very efficient because it end up callingNilClass === nil
which pretty much translates towhich is an alias fornil.is_a?(NilClass)
.Object#==
, so basically it end up doingnil == nil
.However
format.nil?
benefit from a dedicated op code, so it's significantly faster.In this case
Integer#to_s
is much more often called without any arguments,so it's worth optimizing for the most common case.
Ruby 2.7.2
cc @rafaelfranca @kaspth in case you'd like to take a look. Otherwise I'll merge in a couple days.