In Kotlin's syntax, it is obvious that the primary...
# getting-started
t
In Kotlin's syntax, it is obvious that the primary constructor is called before any statements inside the secondary constructor. I think that this is not an advantage but a kind of constraint, but it is still a good thing to make it clear