3 ms·
"If you had to write "extends" in kotlin instead of use a colon, how often would you be doing it?" Certainly more often than you'll need someone to tell you wh
by V-2 8y ago
"If you had to write "extends" in kotlin instead of use a colon, how often would you be doing it?"
Certainly more often than you'll need someone to tell you what ":" in a class declaration does ;)
I see your point, I just don't think this language trait deserves to rank as "confusing" for a professional programmer.
While we're at it, Kotlin, unlike Java, provides explicit "constructor" and "init" keywords. So if it loses points for the lack of "extends", why doesn't Java for not having these?
Nim's manual doesn't seem helpful indeed (they acknowledge it openly in the beginning), but I feel this is sort of beyond the point.
Kotlin's docs are very clear and exhaustive. Case in point - as we discussed inheritance declarations - https://kotlinlang.org/docs/reference/classes.html https://kotlinlang.org/docs/reference/classes.html
- Sir_Substance 8y ago>So if it loses points for the lack of "extends", why doesn't Java for not having these? No one said it didn't :) In general, I personally prefer my languages explicit for a variety of reasons. There's a balance for sure, and one can go too far the other way. For example, I find Rust to be a shade too unwieldy for my optimum preferences, although I would overlook that to gain the safety benefits if I had the right use case.