Re:Open-sourcing Sorbet: a fast, powerful type checker for Ruby
by usrusr on Friday June 21, 2019 @04:04AM
(#20240767)
The eclipse java compiler can be instructed to substitute (most) compile errors with runtime exceptions for those intermediate builds. You still get all the compile time error messages, but the code is ready to run, right up to the point where the compiler complained.
Re:Open-sourcing Sorbet: a fast, powerful type checker for Ruby
by jonnytran on Friday June 21, 2019 @03:58PM
(#20245836)
That's a cool feature. I'd like to see this in other languages and become the norm.
Re:Open-sourcing Sorbet: a fast, powerful type checker for Ruby
by hamilyon2 on Friday June 21, 2019 @09:55AM
(#20242491)
Yes, eclipse java compiler definitely stretches the definition of possible.
Re:Open-sourcing Sorbet: a fast, powerful type checker for Ruby
by teyc on Friday June 21, 2019 @06:15AM
(#20241248)
that's clever, but how does it work?
Re:Open-sourcing Sorbet: a fast, powerful type checker for Ruby
by usrusr on Friday June 21, 2019 @11:52AM
(#20243589)
It doesn't when the error is in something clever you did with the type system (e.g. wildly interdependent generics pretending to be scala).
But for many simpler cases (e.g. the majority of idiomatic java), it can be as simple as substituting an offending imperative line with a throw RuntimeException statement that parrots the compiler error message. I'm sue that they are doing a lot more than that.
Re:Open-sourcing Sorbet: a fast, powerful type checker for Ruby
by astrobe_ on Friday June 21, 2019 @07:35AM
(#20241561)
It looks like what you want is type-mismatch as warnings. I'm not sure it would be viable though, because dynamic languages can throw an exception in this case, while static languages will segfault. Unless the compiler inserts instrumentation code where it saw a type mismatch?
Re:Open-sourcing Sorbet: a fast, powerful type checker for Ruby
by DougBTX on Friday June 21, 2019 @02:42AM
(#20240400)
Yea, that seems like a use-case I’ve felt like I wanted before. TypeScript supports this, as the JS output can be produced even if type checking fails, though in practice I have it turned off so that I don’t accidentally end up with type errors I’ve not fixed.
I ran into this recently when I was working with Rust. And don't get me wrong; I love Rust. But I was experimenting with a new way of doing things in my codebase and was adding a new kind of statistical analysis, and I wanted to run a test case to see what the result was... However, I couldn't because the compiler's typechecking refused to even compile my code, when I knew for a fact that the type errors had nothing to do with the code path of my test case.
I get that that's the whole point of static checking. I can change a large codebase and know exactly when/where I've broken something even if I'm not familiar with all the code, and it will barf at me. But the fact that I can outsmart it, even some of the time, leads me to believe that there will always be a place for dynamic languages.
If 99% of my code has type errors, but there is one code path that is true, who is the compiler to say that that isn't the one code path that I want to take? When experimenting, I build my code dozens of times. The vast majority of the time, I am the only one who consumes the build result. Once in a rare while, I will reach a steady state and build a release. It's really only then that I want the compiler to barf at me and refuse a broken build.
I must not be the only person on the planet who wants to do this sort of thing.