On Mon Dec 5 19:12:45 2022 +0000, Zebediah Figura wrote:
I would advocate for taking the most up-to-date behaviour (especially because it's easier, and more restrictive). We may at some point need to add a compiler switch to turn off that check, but it may make the most sense to just wait until a program actually needs it.
The most up-to-date behavior (10.0.10011.16384) is also the most permissive, since it allows for uninitialized static variables with objects (to which a value can be initialized later) instead of just simply not allowing them.