Convert the gem to frozen string literals #75
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
casperisfine
changed the title
While running tests for sorbet/sorbet#7778 I noticed some deprecation warnings coming from this gem. Ruby 3.4 will have chilled string literals, as a first step toward frozen string literals becoming the default. Ref: https://bugs.ruby-lang.org/issues/20205
casperisfine
force-pushed
the
frozen-string-literal
branch
from
abed200 to
0d2c1e4
Compare
|
Thanks! I'll test that this update works against Stripe's codebase, and will merge if it passes tests. |
qaisjp
approved these changes
May 22, 2024
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
While running tests for sorbet/sorbet#7778 I noticed some deprecation warnings coming from this gem.
Ruby 3.4 will have chilled string literals, as a first step toward frozen string literals becoming the default.
Ref: https://bugs.ruby-lang.org/issues/20205