Wait... you can ship a Go binary that dynamically links with the Go runtime and stdlib at runtime??? Awesome. Can you point me to the docs on this. I’ve always considered the “single binary” taunted feature as somewhat of a limitation because of this.
> On Oct 22, 2018, at 9:41 PM, Ian Lance Taylor <i...@golang.org> wrote: > >> On Mon, Oct 22, 2018 at 7:18 PM, robert engels <reng...@ix.netcom.com> wrote: >> >> I think there is a bigger concern than shipping binaries. I believe that the >> Go stdlib and runtime should be shipped as a shared library, and be field >> upgradable independent of the binaries. This is the only reasonable way to >> to distribute security patches in an efficient and stable manner. >> >> This is another issue, but there is some cross-over with this discussion. > > That already works today. You can ship a shared library, but in order > for the go tool to handle it properly you also have to include the > source. Shared libraries in general are a separate issue from binary > packages. > > Ian > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
