-
Notifications
You must be signed in to change notification settings - Fork 10.5k
[CxxInterop] Import C++ references. #31702
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
Conversation
@swift-ci Please test |
1 similar comment
@swift-ci Please test |
@swift-ci please test Windows platform |
1 similar comment
@swift-ci please test Windows platform |
@swift-ci Please test |
@swift-ci please test Windows platform |
Could you also adjust the incorrect comment in /// Import the type of a function parameter.
///
/// This provides special treatment for C++ references (which become
/// [inout] parameters) and C pointers (which become magic [inout]-able types),
/// among other things, and enables the conversion of bridged types.
/// Parameters are always considered CF-audited.
Parameter, |
e49c60f
to
f8d2be1
Compare
(Adjusted the |
@swift-ci Please test |
1 similar comment
@swift-ci Please test |
@swift-ci Please test |
Progress towards https://bugs.swift.org/browse/SR-12731.
@swift-ci Please test |
1 similar comment
@swift-ci Please test |
@swift-ci Please test Windows |
1 similar comment
@swift-ci Please test Windows |
@swift-ci Please test Linux |
This broke the Windows VS2017 builds: https://ci-external.swift.org/job/oss-swift-windows-x86_64/3976/consoleText |
@compnerd just to double check I understand what happened, this PR passed the windows bot with MSVC19, but then failed on the bot with MSVC17, correct? Is it an option to have MSVC17 bot for presubmits too? |
Correct, that’s what happened. Sadly, I don’t think that adding VS2017 as presubmit is entirely viable (a matter of cost and effort). For the most part it’s not been an issue - this breakage is the first in ~6 months that’s specific to VS2017. |
This PR enables import of C++ references as
UnsafePointers
. PR follows the implementation of pointers with a difference that for references we don't wrap theUnsafePointer
inOptional
.