You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Daniel Martí ab39ee804d fail if the current Go version is newer than what built garble ... For instance, Go 1.18 added support for generics, so its compiler output files changed format to accomodate for the new language feature. If garble is built with Go 1.17 and then used to perform builds on Go 1.18, it will fail in a very confusing way, because garble's go/types and go/importer packages will not know how to deal with that. As already discussed in #269, require the version that built the garble binary to be equal or newer. In that thread we discussed only comparing the major version, so for example garble built on go1.18 could be used on the toolchain go1.18.5. However, that could still fail in confusing ways if a fix to go/types or go/importer happened in a point release. While here, I noticed that we were still using Go 1.17 for some CI checks. Fix that, except for staticcheck. Fixes #269.		3 years ago
..
bench	redesign benchmark to be more useful and realistic	3 years ago
mod	work around a build cache regression in the previous commit	3 years ago
scripts	fail if the current Go version is newer than what built garble	3 years ago