/await:strict and fixes for it#6240
Draft
JohnMcPMS wants to merge 1 commit into
Draft
Conversation
JohnMcPMS
added
the
Next-Release
florelis
approved these changes
May 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📖 Description
/awaitis deprecated; this change removes the CppWinRT injected/awaitand replaces it with/await:strict. When CppWinRT 3.0 is released, we can remove the build props and it should handle things./await:strictcaused a few breaks that are also fixed in this PR, namely:returninstead ofco_returnstd::futurein coroutines that is no longer supported inherently; converted toIAsync*types so CppWinRT coroutine support handles them🔍 Validation
Builds locally, regression tests to ensure functionality.
Microsoft Reviewers: Open in CodeFlow