Update C2345

[Rageking8]

__declspec(align(0)) no longer generates C2345, added a high power of 2 to trigger the error.

[prmerger-automator]

@Rageking8 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[learn-build-service-prod]

Learn Build status updates of commit 24f8a1a:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/error-messages/compiler-errors-1/compiler-error-c2345.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[Court72]

@TylerMSFT

Can you review the proposed changes?

When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

[TylerMSFT]

Could you remove the align(0) example altogether? It's a strange beast because it's not a valid alignment (it's ignored). I tried VS 2022, 2019, 2017, and 2015 and none of them generate the C2345 compiler error. I wonder if that was an error by the original writer. At any rate, I like the other examples but would like to remove align(0) because it muddies the waters.

The spec, N4964 9.12.2 Alignment specifier [dcl.align]/p4 says:

“The alignment requirement of an entity is the strictest nonzero alignment specified by its alignment-specifiers, if any; otherwise, the alignment-specifiers have no effect.”

So let's not use that (align(0)) example.

[learn-build-service-prod]

Learn Build status updates of commit 47e0013:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/error-messages/compiler-errors-1/compiler-error-c2345.md	✅Succeeded

For more details, please refer to the build report.

For any questions, please:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[TylerMSFT]

Thank you!

[TylerMSFT]

#sign-off