Ah nevermind, the fix is to get rid of "return" from my method. There's
probably a bug somewhere related to the repl taking bad input more cleanly,
but this isn't the end of the world once you figure out what the issue is.
Thanks for the time,
Andrew
On Mon, Jun 2, 2014 at 11:35 PM, Andrew Ash
// observed in Spark 1.0
Scala devs,
I was observing an unusual NPE in my code recently, and came up with the
below minimal test case:
class Super extends Serializable {
lazy val superVal: String = null
}
class Sub extends Super {
lazy val subVal: String = {
try {
"l