[jfoster]

Their approach seems reasonable. If they fix this, they will break code that currently works by depending on this. They've not said that they will never fix it, just that they won't for the time being and will reconsider for a future release.

[LanceH]

The fix could be just to issue a warning of non-compliance to C++ standards.

[BudVVeezer]

Except that can break compiling projects as well due to /WX (treating warnings as errors).

[josephlord]

Those projects want to be warned of non-compliant code and they have chosen to have their build break on questionable constructs. I think that this is a weak argument for not issuing a warning.

Having said that the issue looks fairly non-urgent and inclusion in a later release would be perfectly reasonable.