Trivial bugs hurting progress

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On 2015-03-04 08:53 AM, Dimiter Naydenov wrote:
> If it's about catching map ordering issues, let's use go 1.3+ as
> an extra step, rather than gccgo, which is buggy and slow and
> randomly segfaults. It's likely we'll slow down merge gating
> considerably.

It's not just about map ordering issues.  It's about complete
compatibility with GCC Go.  For example, there are issues with test
doubles that have had to be worked around in the past.

When a GCC Go incompatibility is landed, we sometimes spend days with
an unreleasable Juju before it gets fixed.  It has been 3 days since
master was releasable.  Even though GCC Go is slow, it's worth it to
avoid three days of being unreleasable.

My 2¢.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJU9xieAAoJEK84cMOcf+9hDg0H/j6TYPNbI92arsWimT21bxve
1TOBvXtlGJCAwsiZOU//mEKwHXmChrm/a8F2YeWlMDAvk4+Uw4Wid5EViucZiNK9
+IhrpCqG835PMhyxVRbOVzSYoxsjrn1E1Kb5Q+tcOWqrjntoj4JrFMKeCIuANTVj
yi56sl1jNNtOKV0SpmGnILuNNrFVXpy0i4P0Iz462V5sbQ5VtSXwtRc1rtK5OJA6
b47cv346z+DqPJahWNknG+yt2RaGQWzOfTST46B3kiU9CEKsH/U4P3nY9Ixx6hBz
uH8FHpQpfHByK2FPTs9+thnViD30YUaPdFNUnT8FfRnEaNjpqaDEs4jgOafI8LE=
=4tUi
-----END PGP SIGNATURE-----