Thanks. In my top post when I asked about intra-modules optimizations I've naturally meant "compiler produced pre-linking object" modules, but after the discussion I've recognized that I totally missed that "already compiled objects loaded for execution" (i.e. .so or .dlls) are also an important feature for a language that intends to support seriously big projects.
Are there any plans for making ".so" modules in native Go?
> Are there any plans for making ".so" modules in native Go?
Not from the main team, no. They support compiling `.a` library files that can be statically linked, but the authors of Go generally consider dynamic linking to be harmful.[0]
However, because Android development requires `.so` files, the goandroid project[1] contains patches to make go support shared libraries.
Are there any plans for making ".so" modules in native Go?