De: "Jakub Cajka"
> From: "nicolas mailhot"
I'm not generally blaming it on outdated packages(although there
are some), I'm mostly blaming it > on code that is not following best coding
assume some not guaranteed/universal assumptions.
Well, given that Google’s own golang.org/x/debug
fails, I suspect the beast coding
practices Go 1.10 relies on are not that well prevalent.
> On the contrary I suspect some of the packages that pass in your
> obsolete code with disabled unit tests so you're not seeing all the
Can you back it up it? Or is it just your assumption? Actually most
of the failures approx 70% is > occurring in tests(see up mentioned link).
Thus, counting the tests which had not been written yet in the obsolete versions currently
packaged in rawhide, plus all the tests which had never been activated there, it is not
surprising current code with unit tests on sees more failures
And getting rawhide to the point one can actually build current Go apps on it requires
replacing all this legacy code with current versions