Thanks!

I've edited your PR description to say "Resolves" instead of "Solves" - this is because GitHub (as their documentation explains) considers various forms of "Closes", "Fixes", and "Resolves" to be special - using them will "link" a pull request to an issue, such that merging the PR will automatically close the issue. Anything else will "mention" an issue (appearing in its history) but won't set up that auto-closing link. Not a problem, just thought I'd mention it for the future! 😺

Thanks!

I've edited your PR description to say "Resolves" instead of "Solves" - this is because GitHub (as their documentation explains) considers various forms of "Closes", "Fixes", and "Resolves" to be special - using them will "link" a pull request to an issue, such that merging the PR will automatically close the issue. Anything else will "mention" an issue (appearing in its history) but won't set up that auto-closing link. Not a problem, just thought I'd mention it for the future! 😺

Sure! I generally use "resolved", missed this time😬

Apologies for the delay here - we're usually faster at merging PRs, but our process is semi-manual (as we have to mirror GitHub PRs to the internal MSVC repo where the product is officially built) and several members of the team including me have been on vacation 🏖️. I believe we should be able to merge your PR next week, stay tuned.

Thanks for updating this version macro, and congratulations on your first microsoft/STL commit! 🎉 😺