Rectify example in C4178

[Rageking8]

Rectified some errors in the previous example, namely:

• The usage of an uninitialized variable i, which is UB
• The comments on the maximum value being for unsigned int but the type of i is int

The warning is also not emitted with just /W1 and the default settings of a fresh latest VS2022 C++ project. For some reason, the /permissive flag must be set for the warning to be shown. WIth the default of /permissive-, the warning is not emitted even with /Wall and/or /w14178. Not sure if the root cause is some other more granular flag being implicitly set by the permissive flag.

[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 22ecb5c:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/error-messages/compiler-warnings/compiler-warning-level-1-c4178.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

[prmerger-automator]

PRMerger Results

Issue	Description
File Change Percent	This PR contains file(s) with more than 30% file change.

[Jak-MS]

@TylerMSFT

• Can you review this PR?
• IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

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

[TylerMSFT]

Looking into why /permissive is required.

[TylerMSFT]

Thank you. You are correct - the compiler requires /permissive to catch this situation.

[TylerMSFT]

#sign-off