Add sorbet-unwrap command
#2
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
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.
Debugging code with Sorbet signatures is really hard due to Sorbet method wrapping. When stepping through code, one always hits
sorbet-runtimelocations, which is distracting and confusing.This PR adds a
sorbet-unwrapcommand to remove all Sorbet method wrappers from methods. This is again done by reaching intosorbet-runtimeprivate classes and instance variables, but the internals of this part of thesorbet-runtimecodebase seems to be fairly stable.The
READMEis updated with more explanation of what the gem does and how it works.