x == y fails with a NullPointerException when x is null

[smarter]

InterceptedMethods now rewrite x == y into x.equals(y) but this means that if x is null, there will be a NullPointerException, surely that's not the intended behaviour?

[smarter]

I guess the backend should replace equals by calls to BoxesRunTime.equals instead?

[DarkDimius]

No, == needs to be intercepted by backend. It generates code on its own which is slightly more optimized.