On Mon, Feb 26, 2018 at 8:29 AM, Johann Höchtl <johann.hoec...@gmail.com> wrote: > > Right at the beginning of the first post about vgo it is stated: > >> Versioning will also let us ensure that a program builds exactly the same >> way tomorrow as it does today. Even when there are newer versions of my >> dependencies, the go command shouldn't start using them until asked. > > However I did not notice how to specify that a certain compilation unit (set > of modules) requires a certain go version. > > Is this intentional, expected to come over time, to be added at a later point > in time, to be solved somehow differently?
There is a discussion of this at https://golang.org/issue/23969 . 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.
