Originally posted on the Ruby on Rails Blog
Hi there! This is Daniel reporting from Brooklyn, NY.
These two related PRs were opened within a couple hours of each other. The new
optimizer_hints method offers a simple way to
include optimizer hints in your queries. The new
method offers a simple way to annotate your queries with comments.
This PR elegantly ensures that
gsub! methods set back references. I learned a lot about Ruby by
reading through this code and the review comments.
I always enjoy removing code that is no longer needed. It must be especially fun to remove code that includes the comment “I will explain the roflscale so that others will not rm this code.”
Nobody wants a memory leak. Keeping track of these references allows us to garbage collect anonymous subclasses.
I am constantly plagued by bugs related to time. This PR reminds me how complicated time really is.
Has anybody else ever opened a production console session and fogotten to close
it? ✋ Ever done it with the
--sandbox flag and caused your database to run
out of memory? 😭 Thanks, Rails, for protecting me against myself.
Thinking about contributing to Rails? Check out this PR from a first-time contributor for inspiration.