[Canonical-tech] Handling active dependencies in Go

Tue Dec 18 13:25:10 UTC 2012

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

...

> The case brought up was an inconsistent use where there were two
> private functions side by side returning type T, one as pointer and
> one as value. This indicates that there wasn't real consideration
> of which way to go, and was brought up in the review for fixing. It
> was literally a 30 seconds fix, but has proven quite controversial
> somehow.

I didn't feel there was ever disagreement that the return types should
be consistent.

As mentioned, this is a side-track. As the point was to just point out
an example where it is easy to trigger a large API change, and what is
actually required to avoid breaking the build.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (Cygwin)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlDQbrYACgkQJdeBCYSNAAPQAQCfRCzHL4X9LYit984BiVFtYko1
cuYAn2KzUjlX72a+DoHLwdkKiEACuiI4
=02Y7
-----END PGP SIGNATURE-----