[hnthroaway1926]

The default compiler options for java provide a lot of information on null pointer exceptions. I'm sort of blown away that so many on this thread are confounded by NPEs, in my view they are dead simple to track down if you have access to the source.

[_Codemonkeyism]

As I'm running a legacy larger Scala app, what would that compiler options be? e.g. for the line

    service.withName(customer.getName().firstName);

with a NPE in line 25?

[hnthroaway1926]

Break out the line into multiple lines...

String s = customer.getName().firstName;

service.withName(s);

[wtetzner]

So the answer is rewrite your code to work around tooling deficiencies?

I'd prefer this be fixed in the JVM, so you can decide to write your code in the way that's most readable, and not be forced to write it a certain way because the tools suck.

[_Codemonkeyism]

Yes, this is what I'll need to do every time, which is crazy to adapt your code to the tools and then back again.

And it's even

   val n = customer.getName()
   val f = n.firstName
   service.withname(f)

Gladly with Some/None NPEs happen seldom with Scala but they do from interfacing with Java libs from time to time.