[5.9][cxx-interop] evaluate default constructor's unevaluated exception sp… #66477
Conversation
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
…ec if needed when emitting C++ constructor call Fixes swiftlang#65891 (cherry picked from commit b0dab0b)
hyp
changed the title
|
@swift-ci please test |
|
@swift-ci please test source compatibility |
DougGregor
approved these changes
Jun 9, 2023
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.
…ec if needed when emitting C++ constructor call
Fixes #65891
Swift needs to understand if C++ functions are
noexceptto elide exception traps. Some C++ class members, like the implicit default constructor, delay the evaluation of exception specifier. This delay causes Swift to crash on an unevaluated exception specifier. The fix forces Swift to evaluate unevaluated exception specifier for a C++ function that has such an unevaluated specifier.