Skip to content

Conversation

Xazax-hun
Copy link
Contributor

Explanationion: Function pointer types wee always considered fragile in C++ mode, this manifested as a regression when interfacing with glibc.
Issues: rdar://159184118
Original PRs: #84040
Risk: Low, this only removes a spurious error for library evolution.
Testing: Added a compiler test.
Reviewers: @egorzhdan

Explanationion: Function pointer types wee always considered fragile in
C++ mode, this manifested as a regression when interfacing with glibc.
Issues: rdar://159184118
Original PRs: swiftlang#84040
Risk: Low, this only removes a spurious error for library evolution.
Testing: Added a compiler test.
Reviewers: @egorzhdan
@Xazax-hun Xazax-hun requested a review from a team as a code owner September 3, 2025 10:23
@Xazax-hun Xazax-hun added c++ interop Feature: Interoperability with C++ 🍒 release cherry pick Flag: Release branch cherry picks swift 6.2 labels Sep 3, 2025
@Xazax-hun Xazax-hun requested a review from egorzhdan September 3, 2025 10:23
@Xazax-hun
Copy link
Contributor Author

@swift-ci please test

@Xazax-hun
Copy link
Contributor Author

@swift-ci please test Windows

@Xazax-hun Xazax-hun merged commit 4a394fc into swiftlang:release/6.2 Sep 4, 2025
5 checks passed
@finagolfin
Copy link
Member

@Xazax-hun, should we submit this for the 6.2.0 and 6.2.1 branches too, so it doesn't regress with the upcoming 6.2 release?

@Xazax-hun
Copy link
Contributor Author

Xazax-hun commented Sep 9, 2025

I am afraid the ship for 6.2.0 has sailed. Can try 6.2.1.

@Xazax-hun
Copy link
Contributor Author

Opened PR: #84164

@finagolfin
Copy link
Member

I am afraid the ship for 6.2.0 has sailed. Can try 6.2.1.

@DougGregor, what do you think: can we get this into 6.2.0 also, so it doesn't regress with that upcoming release?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c++ interop Feature: Interoperability with C++ 🍒 release cherry pick Flag: Release branch cherry picks swift 6.2
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants