Frozen string for entire library#75
Merged
ioquatix merged 2 commits intosocketry:masterfrom Aug 13, 2021
Merged
Conversation
Member
|
We can drop support for 2.5 if it keeps things simple. |
7d1a4ea to
efebf67
Compare
efebf67 to
5eb0bfb
Compare
Contributor
Author
|
So I am not sure how obvious it is, but the
I Was thinking perhaps for this case
|
This was referenced Jun 6, 2022
Merged
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
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.
Description
Working on the
String.newhas helped move things forward with a downstream consumer of this library.When I enable frozen strings for the entire library, the tests fail.
Types of Changes
This currently removes Ruby
2.0,2.1,2.2,2.3and2.4(early 2013-late 2016)[Edit] At the request of @ioquatix this now also removes Ruby 2.5 to keep CI simple. For anyone interested in 2.5 see commit and more specifically orphaned commit from fork of this repo
Testing
Failing test summary
By mutating inputs, there is more load on downstream consumers of the library. This might require documentation on safely using the library, or
.dupcalls within the library