Fix error pattern to capture and set the COM error info when crossing ABI boundaries #250
Conversation
This file contains 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
…OM error info state correctly across boundaries.
tristanlabelle
force-pushed
the
SwiftRestrictedErrorInfo
branch
from
e66a03a
to
c78eae8
Compare
tristanlabelle
changed the title
tristanlabelle
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Rename
COMErrortoErrorWithHResultandHResult.ErrortoCOMError.Rename
throwIfFailedandcatchtofromABIandtoABI, the former capturing the error info and the latter setting it back.Added
COMErrorandWinRTErrorinitializers taking a message and constructing an error info internally.Fixes #236
Fixes #249
Fixes #254