Skip to content

disable MSVC warning C5105 #42

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 18, 2022
Merged

Conversation

QuietMisdreavus
Copy link

On Windows SDK version 10.0.17763.0, the SDK headers spuriously trip this warning. since swift-cmark itself doesn't emit this warning on its own, disabling this warning will allow it to be built with this SDK (which is the currently active Windows SDK in Swift CI).

on Windows SDK version 10.0.17763.0, the SDK headers spuriously trip
this warning. since swift-cmark itself doesn't emit this warning on its
own, diabling this warning will allow it to be built with this SDK.
@QuietMisdreavus
Copy link
Author

cc @compnerd this is the issue i pinged you about this morning

Copy link
Member

@compnerd compnerd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like a reasonable way to handle it if it resolves the issue.

@QuietMisdreavus
Copy link
Author

It seems to have solved it. I added this commit to the branch being built by swiftlang/swift#40188 and the Windows test finally passed (though the toolchain is failing for unrelated reasons that you've already caught).

Copy link

@daniel-grumberg daniel-grumberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@QuietMisdreavus QuietMisdreavus merged commit 792c1c3 into gfm Mar 18, 2022
@QuietMisdreavus QuietMisdreavus deleted the QuietMisdreavus/windows-warnings branch March 18, 2022 16:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants