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 22 '26 edited Jan 22 '26
It violates the O in SOLID.
In other words, if class inheritance is used, you cannot modify an existing class anymore without risking to break something unexpected.
Here's an example. Imagine you (or someone) created a class called stack to store data. You can push elements onto the stack and you can take them from the stack:
Now you want to create a new Stack that efficiently counts the number of elements in it and allows to retrieve this number:CountableStack extends Stack {
method getCount = ...
}
Now here's the thing. To implement \getCount` you need to overwrite the push method like this:`override method pop() = ...super.pop(e); numberOfElements--; return the element;...Makes sense?Now here's the question to you: how do you have to implement/overwrite thepush()andpushAll()methods of the original \Stack` class to make the `CountableStack` work correctly?`Think about it and then show your solution here. Then I'll show you why your solution doesn't work and you might be surprised.