On Mon, May 16, 2022 at 08:46:31PM +1200, Thomas Munro wrote:
> Looking at the published lifecycle info, 2017 is the oldest still in
> 'mainstream' support[4], so it wouldn't be too crazy to drop VS 2015
> too, just like those other projects. That said, it sounds like there
> is no practical benefit to being more aggressive than you are
> suggesting currently (as in, we wouldn't get to delete any more crufty
> untestable dead code by dropping 2015, right?), so maybe that'd be
> enough for now.
FWIW, one of my environments is using VS2015, because I have set it up
years ago and I am lazy to do this setup except if I really have to :)
The code works as far as I know, still I am not really excited about
cutting support for more versions than necessary, particularly as this
does not simplify the C code more.
--
Michael