-
-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Enable recursive typechecking in specs #20644
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
673dea3
to
0fbb5f9
Compare
a41154e
to
ef60d2e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a great idea!
924a4ed
to
56ce625
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm good to land this if/when you are.
Sounds good, this still needs some work though (I want to limit this to specs for now, it's currently turned on globally for my own convenience. The commits also need to be squashed. I want to make a final pass that the updates make sense (I made a couple small changes last night), and elaborate in comments/todos where I've undertaken some light refactoring.) |
1f8a945
to
eeabdfe
Compare
bc49416
to
cd8688f
Compare
cd8688f
to
a5ca197
Compare
6884770
to
de72b6d
Compare
de72b6d
to
7b2171a
Compare
I confirmed in the sorbet slack that this is the best approach currently available. Opening for re-review for anyone who wants to take a look, otherwise i'll merge within the next day or so. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @dduugg, great work here!
This may have caused this bug, reported by multiple users (including me): #20703
|
brew style
with your changes locally?brew typecheck
with your changes locally?brew tests
with your changes locally?Just prototyping, curious what happens if we enable recursive typechecking in specs. (Feel free to comment if you think this is or isn't a valuable route to pursue further.)
This is done via 🐒-patching due to sorbet/sorbet#3800