clang format validation failed. run clang-format (from IDE or standalone) and update

Additionally:

• Please edit your PR title to describe (very briefly) what your change is doing - mentioning issue numbers there is not useful. PR titles become part of git history (e.g. see git log or the graphical gitk), and a long series of "solve issue #nnnn" is completely opaque. "Update list to remove bogus strengthened comment" would be perfectly descriptive, or you can phrase it another way.
• Please edit your PR description to use GitHub's fix/close/resolve syntax so that your PR is properly linked to the issue that it resolves. "Fixes #nnnn", "Resolves #nnnn", or "Closes #nnnn" are all fine.

Thanks!

You still haven't ran clang-format.

If you are trying to do commit using web interface only then I want to tell that this is generally not a path forward.
Whereas you may be able to finish this change this way, it doesn't let you get any further, when you have to test and validate your changes locally. I recommend you learning how to use a Git/Github client and following README.md steps to build this locally.

(I admit I have done some web commits on my own, but the purpose of good first issue is for a contributor to learn the workflow; using web interface defeats this purpose)

You still haven't ran clang-format.

If you are trying to do commit using web interface only then I want to tell that this is generally not a path forward. Whereas you may be able to finish this change this way, it doesn't let you get any further, when you have to test and validate your changes locally. I recommend you learning how to use a Git/Github client and following README.md steps to build this locally.

(I admit I have done some web commits on my own, but the purpose of good first issue is for a contributor to learn the workflow; using web interface defeats this purpose)

sure sir, actually i tried with some online clang formatters(they have shown that code is formatted correctly) and some vs code extensions, but haven't looked in depth
will try now and update by end of the day
thanks for your suggesions :-)

runned it locally

Thanks! I went ahead and edited your PR description to use GitHub's fix/close/resolve syntax.

This PR will be part of our next merge batch, likely next week. I'll post comments as I prepare your PRs for merging.

I'm mirroring this to the MSVC-internal repo - please notify me if any further changes are pushed.

Thanks for the fix, and congratulations on your first microsoft/STL commit! 🎉 🐈 😸

This change is expected to ship in VS 2022 17.13 Preview 2.