----- Original Message -----
> From: "Florian Weimer" <fwei...@redhat.com>
> To: "Jakub Cajka" <jca...@redhat.com>
> Cc: golang@lists.fedoraproject.org
> Sent: Wednesday, March 13, 2019 10:58:16 AM
> Subject: Re: [golang-dev] proposal: public module authentication with the Go
> notary
>
> * Jakub Cajka:
>
> > From the Fedora perspective it is due to the stability of the upstream
> > code(API changes) there is nearly no effective difference compared to
> > the non shared(you will have to rebuild "everything" anyway). I have
> > been toying for a long time with switching at least sdtlib to be
> > dynamically linked in the BR, but haven't got around to push it
> > out(i.e. coerce maintainers to BR it, IMHO we have bigger nuts to
> > crack atm).
>
> I don't think linking the run time dynamically is feasible.
>
> The Go 1 compatibility strategy does not mention not adding private
> fields to structs as a breaking change, for example:
>
> <https://golang.org/doc/go1compat>
>
> But each time you allocate a struct, the caller inlines the size, so
> adding private fields is very much a breaking change.
>
> Thanks,
> Florian
This is not(shouldn't be) a runtime, just the standard library.
JC
> _______________________________________________
> golang mailing list -- golang@lists.fedoraproject.org
> To unsubscribe send an email to golang-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/golang@lists.fedoraproject.org
>
_______________________________________________
golang mailing list -- golang@lists.fedoraproject.org
To unsubscribe send an email to golang-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/golang@lists.fedoraproject.org
