Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> There's nothing new in terms of keywords about (implicit using or file scoped namespaces)

And I didn't imply that they were new keywords, they were examples of the second category, "new ways of doing things". The text "do the same thing" alludes to that.

> and makes code more readable and shorter, that's it.

Correct, but each new ways of doing things comes at the cost of there now being (at least) two ways to do the same thing.

> It just simplifies stuff, can we honestly call it an expansion of language?

If a source file that was not legal in language version 9, is now legal in language version 10, then yes we honestly can and must call it that. It is literally an expansion of the subset of all possible source files, that are legal source files in the language.

Does it "simplify stuff" if there are now 2 ways of doing a thing, when previously there was only one? The parser has to deal with both now. It depends on how you look at it, I think. e.g. It depends on if your code mixes them. If not then the code can be simpler, but as coders we have to still know both as we might encounter both.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: