Re: Migration tooling and the cumulative cost of purely syntactical deprecations

On Fri, Oct 11, 2019 at 12:25:11PM +0200, Nikita Popov wrote: > Rather than starting a holy war over every single RFC that contains the > word "deprecation", I think we should take a look at our migration story > and possibly invest some effort into creating a "blessed" tool for this > purpose: One that only performs migrations that are completely safe and > should be runnable without fear of breaking code. > > I do realize that there is already quite a bit of existing tooling, things > like Rector, various CS fixers and compatibility scanners, but I don't > think that we have anything that just works out of the box to do what is > safe and no more. Could I suggest an option for it to point out where other (unsafe) migrations could/should be done so that we know where to look. -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 https://www.phcomp.co.uk/ Parliament Hill Computers Ltd. Registration Information: https://www.phcomp.co.uk/Contact.html #include <std_disclaimer.h>