Jon Pretty

‘Primitive null’ sounds very much like an insult to null, which I approve.

But, did you see that it's finding the implicit in B, not the one in A? You can delete the trait, extends and override and you get the same answer.

Ah, yes of course. I've minimized the example from a real case that happened at work, but it's not as minimal as I thought!

I mean, val a: Int = a is even more minimal!

Holy, does that compile? I thought implicit search was part of the issue

val a: Int = a, step-by-step: 1. First ask the JVM for an empty int-field 2. Now, calculate the value to set it to 3. Look up the value in the field, a; turns out it's 0 4. Save the result in the field, a

Would be expect a different result in Scala.js or Scala native?

The empty field values are decided by the runtime, so at least in theory I wouldn't rule out the chance of a different result. I don't think there's a shared spec.