Sorry if it’s been asked before, but this is the first (admittedly nit-picky) “Huh?” question that jumped out at me as I’ve been perusing the Kotlin reference. It seems to me that the
val keyword in the
const val declaration is completely superfluous, since a compile-time constant is by definition just that much more immutable.
Can someone clarify the rationale behind this salty bit of syntax? Thanks.