News for hackers. Stuff that matters.
Re:The Ergonomics of Type Checking (2016) by twic on Saturday October 28, 2017 @04:13PM (#15576584)
You can do something similar with Eclipse's compiler for Java, JDT, which features [1]:

An incremental Java compiler. Implemented as an Eclipse builder, it is based on technology evolved from VisualAge for Java compiler. In particular, it allows to run and debug code which still contains unresolved errors.

That means that you can write something like:

    private void describe(String string) {
        if (string.isEmpty()) empty();
        else nonempty(string);
    }
    
    private void empty() {
        System.out.println("empty");
    }
    
    private void nonempty(String string) {
        System.out.println("contains " + string.size() + " characters");
    }

Then you can still run the code and call describe, but if execution reaches nonempty, you get a runtime error telling you about the compilation problem.

It's one of the few things from Eclipse i miss when using IntelliJ.

[1] http://www.eclipse.org/jdt/core/

Re:The Ergonomics of Type Checking (2016) by exceptione on Saturday October 28, 2017 @06:33PM (#15577023)
I can't see a problem with nonempty, am I stupid?
Re:The Ergonomics of Type Checking (2016) by Thiez on Saturday October 28, 2017 @07:53PM (#15577305)
A `String` in Java has a `.length()`, not a `.size()`.
Re:The Ergonomics of Type Checking (2016) by twic on Sunday October 29, 2017 @12:44PM (#15579990)
Apologies! I meant to include a comment pointing out the error (as Thiez writes, it should be length, not size), but that somehow didn't make it into the comment as published. I blame my sub-editors, can't find the staff these days.
Re:The Ergonomics of Type Checking (2016) by _pmf_ on Saturday October 28, 2017 @04:27PM (#15576625)
And this has been working for a decade. It's one of the reasons I laugh in their face when a JS developer tries to sell his babel reload crap as progressive.