On 03/04/2018 03:42 AM, Jacob Carlborg wrote:
Aha, you mean like that. Seems a bit difficult to fix. Perhaps specifying a range of compiler versions would do?
Yea, there's really no two ways around it: Ultimately, each new compiler release will need to get added to .travis.yml (or any other CI's equivalent) either sooner or later. (Unless the project eschews anything beyond "latest versions ONLY", but that comes with its own downsides, especially for libraries.)
Luckily, this is definitely automatable, at least as far as auto-submitted PRs, if nothing else. The devil is just in the details.
