potato-peeler
an hour ago
One of the things go makes it simple to do is help a reader understand which constructs belong to which package, since any use of external imports is prefixed by the package name.
In go, if I don’t know a constructs definition, i know exactly where to look at and find it.
When exploring a new language I won’t always setup an ide first. I just want to look at the documentation on my own. Heck, any language which requires ide or any mandatory tooling to work with it, is already handicapping a developer.
G# seems to copy go syntax but didn’t copy the things that go makes it easier to understand any go code.
torginus
an hour ago
Agree, and this is a huge bungle you can make in language design, that will affect compiler performance down the line significantly.
If you know which package each type comes from, you only need to check the exports of that package, otherwise its a local.
Otherwise you have to start compilation by building up a list of every package and its exports. This is particularly bad for incremental compilation, and starts to drag on large projects.
The saving grace of .NET in this case is that most .NET programs traditionally didn't have that many imports. You have mscorlib for the framework itself, which is almost all the basics, and maybe ASP.NET and a dozen other small packages.
But this doesn't have to be the case, and if you have thousands of small packages (because your app is huge), then your performance tanks.