Handle module/external packaging with nuget

[stevefan1999-personal]

I love the idea of this project to compete with Golang, but I don't think there is a neat way to resolve external dependency problem. Unfortunately, this also mean you'd have to implement some kind of module support, just like Go Modules, which is a hot mess. In Golang you can just import from GitHub, but in .NET world most of us use nuget. More specifically, should we pull the nuget manifest every time we see one in the parent directory and link it this way?

Related: #1 but specifically targeting nuget

[MichalStrehovsky]

NuGet implies MSBuild and at that point one is better off using dotnet - this is not trying to be a replacement of dotnet, but a very simple/low-dependency way to compile C# source files to simple/low-dependency executables.

Some people like the Go Modules hot mess and this is just about having those options.