This will likely get fixed upstream. The change that went it to get gc and gccgo to work the same broke the behavior not only of goyaml, but also of the stock encoding/json package, and likely many other marshaling packages out there. There's already partial agreement from the core team that this is not okay and must be addressed before Go 1.3.
This will likely get fixed upstream. The change that went it to get gc and gccgo to work the same broke the behavior not only of goyaml, but also of the stock encoding/json package, and likely many other marshaling packages out there. There's already partial agreement from the core team that this is not okay and must be addressed before Go 1.3.