Fix frozen string literal warning #125
Open
Conversation
This file contains hidden or 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
Ruby 3.5+ will enable frozen string literals by default which causes the following warning on Ruby 3.4.2: warning: literal string will be frozen in the future (run with --debug-frozen-string-literal for more information) The fix is to use a mutable string. This syntax is supported since Ruby 2.1, thus backwards compatible.
|
I'm getting the same issue. 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Ruby 3.5+ will enable frozen string literals by default which causes the
following warning on Ruby 3.4.2:
warning: literal string will be frozen in the future (run with
--debug-frozen-string-literal for more information)
The fix is to use a mutable string. This syntax is supported since Ruby
2.1, thus backwards compatible.