News for hackers. Stuff that matters.
Re:Google Go: The Good, the Bad, and the Meh by CJefferson on Monday February 11, 2013 @03:45PM (#5203089)
Actually, I find public->private is not a breaking change, because before I do a 'public->private' change, I first remove all the public calls. Therefore, all I have left to do is to check the in-class calls.
Re:Google Go: The Good, the Bad, and the Meh by alanctgardner2 on Monday February 11, 2013 @06:43PM (#5204209)
That's great for you, but I suppose you've never published a module on CPAN, a ruby gem, a Python... egg (man, that's a weird convention). As soon as someone else depends on your module - and Go is very modular, this behavior is encouraged - suddenly it's an exercise in putting fluids back into containers, or whatever they say.