Account for new identity comparison hashes in Sorbet internals #1732
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.
Motivation
The build in main is still breaking because of the changes in sorbet/sorbet#7531.
Now that the hashes are compared by identity, we can no longer use the
object_id
to figure out if a signature is final or not.Implementation
I added a feature check so that we decide what to do based on the Sorbet version.
We couldn't force the hash to be compared by identity without breaking Sorbet's own internals, so I don't think there are any other approaches we can take.
Tests
Existing tests should continue to pass.