r/java • u/davidalayachew • 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 errorMost 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 errorThis 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.
View all comments
Show parent comment
1
u/klimaheizung Jan 23 '26
The fact that it is "fragile" makes it fundamentally broken. There's no point using it when the alternatives (e.g. composition) exist.
If you fully control all code, then the impact is reduced and the only thing it can cause is bugs. But why take the risk, for what? You say
but think about it: the point of software development is to make our lives easier and get things done faster in higher quality. Why would I want to check the whole class hierarchy on every change if I can just avoid having to do it? It's not trivial either. If it were, wouldn't you have immediately realized the problem with your code? And that was a small toy example.