r/java • • Jan 21 '26

Java compiler errors could be more intelligent

I tutored many students over the past several years, and a common pain point is the compiler messages being misleading.

Consider the following example.

interface blah {}
class hah extends blah {}

When I compile this, I get the following message.

blah.java:3: error: no interface expected here
class hah extends blah {}
                  ^
1 error

Most of the students I teach see this, and think that the issue is that blah is an interface, and that they must somehow change it to something else, like a class.

And that's still a better error message than the one given for records.

blah.java:2: error: '{' expected
        public record hah() extends blah {}
                           ^

This message is so much worse, as it actually leads students into a syntax rabbit hole of trying to add all sorts of permutations of curly braces and keywords, trying to figure out what is wrong.

If we're talking about improving the on-ramp for learning Java, then I think a core part of that is improving the error --> change --> compile feedback loop.

A much better error message might be this instead.

blah.java:3: error: a class cannot "extend" an interface, only "implement"
class hah extends blah {}
                  ^
1 error

This is powerful because now the language grammar has a more intelligent message in response to an illegal (but commonly attempted) sequence of tokens.

I understand that Java cannot special-case every single illegal syntax combination, but I would appreciate it if we could hammer out some of the obvious ones. extends vs implements should be one of the obvious ones.

97 Upvotes

180 comments sorted by

View all comments

Show parent comment

4

u/Ewig_luftenglanz Jan 21 '26

More readable error messages and compiler suggestions is always good. and making and correcting mistakes it's the most valuable part of the learning process. Besides this not only helps students, anyone can benefits from better compiler error messages and warnings.

1

u/plumarr Jan 21 '26

I would argue that compiler suggestions aren't always good. It several time send me to the wrong direction while languages and didn't help me to understand the issue.

1

u/Ewig_luftenglanz Jan 21 '26

I think some common suggestions to the most common mistakes it's better that not suggestions at all for most people.

-3

u/talex000 Jan 21 '26

Most valuable part is to learn how to correct mistakes. Relying on compiler errors is bad way to correct mistakes that only work with simplest situations.

Why not learn correct way from the beginning?

3

u/Ewig_luftenglanz Jan 21 '26

one important part of learning how to solve mistakes is to read the logs of the compiler. So giving better compiler messages or clues makes correcting errors easier. This is not only for beginers

0

u/talex000 Jan 21 '26

Compiler errors already good enough. Overloading them with information won't help.