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
Replace sorbet-runtime-stub with sorbet-runtime #13566
Conversation
Review period ended. |
bb0d0f9
to
c2ed256
Compare
Cop out fix is to roll it in with the next Sorbet version bump but we should probably fix it properly. |
66b340b
to
e2109d5
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.
One comment about more comments but otherwise seems fine thanks 👍🏻
Yeh, that'd be good.
Maybe needs an explicit |
|
Ah looks like Bundler might have finally fixed the extensions directory mess in the standalone Not really relevant to this PR but good to know nonetheless. Edit: ok it maybe doesn't cover the platform part yet but it's a start. |
Pushed a Sorbet update here since I don't really know how to handle bundle cleanup without breaking everything. This should be sufficient to pass CI. |
Resolves #11521.
This does have more overhead than the stub but I'm not convinced it's noticeable. I've done a monkey patch disabling some more common parts of runtime checking though to be on the safer side.
If the overhead is not much, we could expxand this in the future by not doing these monkey patches and doing things such as a one-pass basic evaluation of
sig
blocks to allow for example abstract classes to work if we want to make use of them. We don't need to commit to full level runtime checking to do this - there's different levels on the spectrum.Should be able to replace #13563 if the user does
brew install-bundler-gems --groups=
first to clear previous settings. I would still however like information to fix the install error some people have since it'll still be an issue forbrew typecheck
. I cannot reproduce the issue myself.