I'm wondering if anyone is encountering the same error we are with Scala, or if (hopefully) this is a known problem...
The problem occurs when creating an instance of a class with about 20 var. The error is random and occurs [significantly] less than one time in a million instance creations. In particular, for us it is occurring when we create a reactor and send it a message. Apparently the reactor starts processing the message before all of its variables are initialized.
scala.UninitializedFieldError: Uninitialized field
We do have a work around--don't use a null initial value:
var longMsgType: Option[String] = None
This complicates our code a bit, and we are loath to use it in all our code.
Ideas? Comments? Suggestions?
We're using Scala RC6. Is chckinit turned on by default? Can we turn it off???
Bill