News for hackers. Stuff that matters.
Re:Introduction to Go 1.1 by laumars on Tuesday March 26, 2013 @06:40AM (#5442285)
It's the term "strongly" that concerns me as that's not really a guarantee. However I think I will take your advice and start development on it regardless (if I've written it correctly, then any breaking changes will be confined to their respective module so fixing them shouldn't be much of an ordeal).

Thanks for the feedback :)

Re:Introduction to Go 1.1 by dchest on Tuesday March 26, 2013 @07:02AM (#5442370)
See http://golang.org/doc/go1compat.html for details on compatibility.
Re:Introduction to Go 1.1 by enneff on Tuesday March 26, 2013 @11:53AM (#5444099)
It is a guarantee. I promise, you won't have to change any of your code when updating from 1.0 to 1.1.
Re:Introduction to Go 1.1 by ithkuil on Tuesday March 26, 2013 @03:19PM (#5445446)
True. Except if you used ListenUnixgram returned and couldn't use type inference for storing it's return value. Go1.0 returns UDPConn, which will be renamed as UnixConn.

This is a clear API bug, and it's the only exception to the backward compatibility rule.