Skip to content

[Runtime] Change the unowned reference fatal error to "was already destroyed." #81041

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

Merged
merged 1 commit into from
Apr 28, 2025

Conversation

mikeash
Copy link
Contributor

@mikeash mikeash commented Apr 23, 2025

The "was already deallocated" message is incorrect, since the target of an unowned reference stays allocated even after being deinitialized. We could say "was already deinitialized" but that's a bit of a niche term. "Was already destroyed" conveys what happened without the reader needing to worry about deinitialization versus deallocation.

rdar://149237704

…stroyed."

The "was already deallocated" message is incorrect, since the target of an unowned reference stays allocated even after being deinitialized. We could say "was already deinitialized" but that's a bit of a niche term. "Was already destroyed" conveys what happened without the reader needing to worry about deinitialization versus deallocation.

rdar://149237704
@mikeash mikeash requested a review from al45tair as a code owner April 23, 2025 19:33
@mikeash
Copy link
Contributor Author

mikeash commented Apr 28, 2025

@swift-ci please test

@mikeash mikeash enabled auto-merge April 28, 2025 16:28
@mikeash mikeash merged commit 22c34dd into swiftlang:main Apr 28, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants