Jake Zimmerman

We have a policy of testing changes to Sorbet against Stripe's codebase before merging them. I've kicked off a test run for the current PR. When the build finishes, I'll...

We have a policy of testing changes to Sorbet against Stripe's codebase before merging them. I've kicked off a test run for the current PR. When the build finishes, I'll...

For what it's worth, this is a runtime error already: ``` ❯ ruby foo.rb Traceback (most recent call last): 10: from foo.rb:4:in `' 9: from foo.rb:6:in `' 8: from /home/jez/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/sorbet-runtime-0.5.6052/lib/types/private/methods/_methods.rb:228:in...

Thank you for the detailed report!

The dead code error is a symptom of a larger problem, which is that Sorbet thinks that the `x` has type `{x: Integer, partial: T::Boolean}`. Here's a more minimal repro:...

Another idea: this might be slightly easier for cases where one keyword argument has already been provided, because then we can change the parser to parse the file like ```...

In a debug build, it crashes with an assertion failure. ``` ❯ lldb -- sorbet bar.rb (lldb) target create "sorbet" Current executable set to 'sorbet' (x86_64). (lldb) settings set --...

> fast-follow those updates fwiw, I think it should be fine to write the docs and link ahead of time, and fast-follow with a correction to the docs if the...

I posted this on a Slack discussion thread before landing the change, but wanted to preserve the history in a comment, so here it is: - - - - -...

It's worth noting that as soon as you start to type a class name, the issue resolves itself: #### Input [→ View on sorbet.run](https://sorbet.run/?arg=--print=parse-tree-whitequark#%23%20typed%3A%20true%0A%0Aclass%20Before%3B%20end%0A%0Aclass%20Outer%0A%20%20X%20%3D%201%0A%20%20def%20example%3B%20end%0A%20%20class%20A%0Aend) ```ruby # typed: true class Before;...