3 ms·
> This is a noob mistake, not a huge mystery. The interesting part is why it worked in VS2013 but failed in VS2022.
by D13Fd 2y ago
> This is a noob mistake, not a huge mystery.
The interesting part is why it worked in VS2013 but failed in VS2022.
- wakawaka28 2y ago>The interesting part is why it worked in VS2013 but failed in VS2022. I thought the explanation he came up with was interesting but such a change could have easily been brought about by changes to reallocation parameters in the implementation.