I like this proposal. For unmaintained code that needs fixing when incompatible changes are introduced, I wouldn’t make the toolchain increasingly complex thoug

I like this proposal. For unmaintained code that needs fixing when incompatible changes are introduced, I wouldn’t make the toolchain increasingly complex though. It‘d be better to just fork it and have it fixed by volunteers (or bots!), then put in some canonical location (e.g. github.com/go2compat/oldhost.org/olddir/...) so developers can just try to change the include path as a standard solution on such compile errors. This is more feasible now than 15 years ago since even unmaintained code is usually public on github or similar. It would help to break as few things as possible in this case, but that seems to be the intention anyway.