4 ms·
Man i gotta disagree with almost all points in this article. Name-Shadowing is confusing? Should be common sense to not have multiple variables with the same n
by tabs_masterrace 8y ago
Man i gotta disagree with almost all points in this article.
Name-Shadowing is confusing? Should be common sense to not have multiple variables with the same name in the same scope.
Optionals are ugly in Java-Interop, so we decided to just use Java instead. Great reasoning.
- choward 8y ago> Name-Shadowing is confusing? Should be common sense to not have multiple variables with the same name in the same scope. You're saying name-shadowing isn't confusing because it should be common sense not to use it? Then why not just enforce that in the language?
- apatrida 8y agoThere is an issue in the Kotlin issue tracker to be able to turn warnings into errors, and it was created by a Kotlin team member specifically for this name-shadowing case. So, you will be able to turn any specific warning into an error once this is implemented. Which is nice, I like 0 warnings.