null?
-
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
-
-
Any reason why the compiler allows such a circular reference? It's seems pretty easy to catch, but I'm sure I'm missing the complications.
-
You'll have to ask the compiler engineers. There are some limited checks in place for similar situations: > def x: Int = x <console>:11: warning: method x does nothing other than call itself recursively
- Show replies
New conversation -
-
-
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.
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.