On 12/24/2019 01:39 AM, Philip Race wrote: > Have you verified this with VS 2017 ? > Not that I can see a problem but I doubt we want to trade breaking 2017 > to fix 2013 ... Yes, VS 2017 compiles fine with this fix. > > [...] > -- -Alex