the other two no-params messages are case classes with no params rather than case objects - any reason to be inconsistent?

there is a painful runtime failure in the future if you ever add params to a case object, because `case Foo` still compiles if `Foo` is a case class, IIRC. since the object exists too. I was thinking that was why we had no-params case classes but I was just making that up...