Re: breaking changes vs legacy: how gofix solved the problem with automated code transitions

2013-05-26 Thread Andrej Mitrovic
On 5/26/13, timotheecour wrote: > This is what we need for D if we want to avoid getting stuck in > this dilemma. It's good for fixing 99% of the cases. But don't forget we also have string mixins (and string imports), which can't easily be fixed. Because of that we shouldn't allow ourselves to b

Re: breaking changes vs legacy: how gofix solved the problem with automated code transitions

2013-05-26 Thread Paulo Pinto
Am 26.05.2013 08:32, schrieb timotheecour: There is a dilemma of having to choose between: A) getting stuck with bad names / apis / language issues forever B) making painful breaking changes that breaks existing code See recent D threads for all the polemics this creates on (in)stability of D.