Fix rubocop redundant freeze warnings#5468
Conversation
53bb76d to
3970bc8
Compare
7a97e8f to
655de48
Compare
96eccbf to
a534e2a
Compare
|
I had to do a painful rebase on this one, and easily could have made a mistake. So once #5447 is merged and this is rebased on top of that, do a careful inspection of the changes to ensure I didn't screw it up. |
a534e2a to
50bd13a
Compare
There was a problem hiding this comment.
Discovered this while looking at a related git blame... This could be pulled into a separate PR, but since just this small comment I thought okay to shoehorn into this PR.
There was a problem hiding this comment.
How about we create a new draft PR that makes the change suggested by the TODO, and then we can pull that in when we're ready for it?
There was a problem hiding this comment.
good idea, I'll open a draft PR shortly... I'd also like to leave in the code comment so that we don't lose track of it...
46efc29 to
a77350a
Compare
9a0f9ee to
feaacf9
Compare
There was a problem hiding this comment.
Was this included by accident?
feaacf9 to
c7af02c
Compare
|
Merging once passes CI as this lint rule is super safe fix |
ca558b9 to
c6691c7
Compare
Rubocop is warning about things that are double frozen, ie `.freeze` is redundant. These warnings started showing up as part of the Ruby 3.1 upgrade, and were excluded from that PR in order to minimize noise. So this fixes them. Co-authored-by: Mattt <mattt@github.com>
c6691c7 to
fd64bac
Compare
Fix Rubocop freeze warnings.
Rubocop is warning about things that are double frozen, ie
.freezeis redundant.These warnings started showing up as part of the Ruby 3.1 upgrade, and
were excluded from that PR in order to minimize noise.