-
Notifications
You must be signed in to change notification settings - Fork 10.4k
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
Assertion failure swift::ProtocolConformanceRef::subst with 6.1 in release build #79318
Comments
#70834 looks similar, but unsure it is exactly the same. |
rdar://146101172 |
Same stack with Xcode 16.3 Beta 3:
|
Related forums thread: https://forums.swift.org/t/proper-way-to-escalate-swift-6-1-crash-blockers/78620 Copying my response
Thanks for the ping here, I'll see what I can find out. |
Fix incoming soon: #80109 |
…s requirements This is a narrow fix, we are going to work on fixing this properly and allowing both devirtualization and specialization for distributed requirement witnesses. Anything that uses an ad-hoc serialization requirement scheme cannot be devirtualized because that would result in loss of ad-hoc conformance in new substitution map. Resolves: swiftlang#79318 Resolves: rdar://146101172
…s requirements This is a narrow fix, we are going to work on fixing this properly and allowing both devirtualization and specialization for distributed requirement witnesses. Anything that uses an ad-hoc serialization requirement scheme cannot be devirtualized because that would result in loss of ad-hoc conformance in new substitution map. Resolves: swiftlang#79318 Resolves: rdar://146101172 (cherry picked from commit 0415b40)
…s requirements This is a narrow fix, we are going to work on fixing this properly and allowing both devirtualization and specialization for distributed requirement witnesses. Anything that uses an ad-hoc serialization requirement scheme cannot be devirtualized because that would result in loss of ad-hoc conformance in new substitution map. Resolves: swiftlang#79318 Resolves: rdar://146101172 (cherry picked from commit 0415b40)
…s requirements This is a narrow fix, we are going to work on fixing this properly and allowing both devirtualization and specialization for distributed requirement witnesses. Anything that uses an ad-hoc serialization requirement scheme cannot be devirtualized because that would result in loss of ad-hoc conformance in new substitution map. Resolves: swiftlang#79318 Resolves: rdar://146101172 (cherry picked from commit 0415b40)
…s requirements This is a narrow fix, we are going to work on fixing this properly and allowing both devirtualization and specialization for distributed requirement witnesses. Anything that uses an ad-hoc serialization requirement scheme cannot be devirtualized because that would result in loss of ad-hoc conformance in new substitution map. Resolves: swiftlang#79318 Resolves: rdar://146101172
…s requirements This is a narrow fix, we are going to work on fixing this properly and allowing both devirtualization and specialization for distributed requirement witnesses. Anything that uses an ad-hoc serialization requirement scheme cannot be devirtualized because that would result in loss of ad-hoc conformance in new substitution map. Resolves: swiftlang#79318 Resolves: rdar://146101172 (cherry picked from commit 0415b40)
…s requirements This is a narrow fix, we are going to work on fixing this properly and allowing both devirtualization and specialization for distributed requirement witnesses. Anything that uses an ad-hoc serialization requirement scheme cannot be devirtualized because that would result in loss of ad-hoc conformance in new substitution map. Resolves: swiftlang#79318 Resolves: rdar://146101172 (cherry picked from commit 0415b40)
…s requirements This is a narrow fix, we are going to work on fixing this properly and allowing both devirtualization and specialization for distributed requirement witnesses. Anything that uses an ad-hoc serialization requirement scheme cannot be devirtualized because that would result in loss of ad-hoc conformance in new substitution map. Resolves: swiftlang#79318 Resolves: rdar://146101172
Description
Preparing for Swift 6.1 adoption and experiencing a compiler crash while compiling in release mode; debug mode works fine.
Adding
Shows:
Reproduction
Stack dump
Expected behavior
Succesful compilation.
Environment
swift-6.1-DEVELOPMENT-SNAPSHOT-2025-02-10
:Also reproduces on
swift-DEVELOPMENT-SNAPSHOT-2025-02-04
:Additional information
No response
The text was updated successfully, but these errors were encountered: