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
[SR-9376] Private CodingKeys in another file messes up Codable synthesis #51842
Comments
Probably not related. That's really scary that it's trying to use the CodingKeys from the other file! Fortunately it's probably an easy fix: we need to do a smarter lookup when synthesizing Codable implementations. |
Yeah sry, I just went through all the other bug reports with the same error and there were only very few open. A poor man's check for related bugs 🙂 |
This still crashes when using Xcode 10.2 in Swift 4.2 compiler mode. Then I even get the crash-reporter popup with the following:
|
Even in Swift 5 this crashes spectacularly |
This still crashes in the latest Swift 5.6 (Xcode Version 13.3.1 (13E500a))
|
Attachment: Download
Environment
Tested with Xcode Version 10.1 (10B61) included toolchain and the latest master (2018-11-28a)
Additional Detail from JIRA
md5: 8fb0cf9840008677d56ea3c469ce3c08
Issue Description:
This traps the compiler when using `incremental` compilation mode but not when using `whole module` mode (see attached sample project for easy testing):
Property.swift
Property+Codable.swift
with the result:
This only happens when the conformance is in a separate file.
Possibly related to https://bugs.swift.org/browse/SR-4370 ?
The text was updated successfully, but these errors were encountered: