You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SR-15938 Error when referencing #dsohandle in a Swift test on Windows
Issue Description:
Reproducer (taken directly from SE-0280 proposal):
protocolDecodingError{staticvarfileCorrupted:Self{get}staticfunc keyNotFound(_ key:String)->Self}enumJSONDecodingError:DecodingError{case fileCorrupted
case keyNotFound(_ key:String)}
When building using Xcode, I get the following error:
<unknown>:0: error: symbol '$s9SwiftTest17JSONDecodingErrorO11keyNotFoundyACSScACmF' (SwiftTest.JSONDecodingError.keyNotFound(SwiftTest.JSONDecodingError.Type) -> (Swift.String) -> SwiftTest.JSONDecodingError) is in generated IR file, but not in TBD file
<unknown>:0: error: symbol '$s9SwiftTest17JSONDecodingErrorO13fileCorruptedyA2CmF' (SwiftTest.JSONDecodingError.fileCorrupted(SwiftTest.JSONDecodingError.Type) -> SwiftTest.JSONDecodingError) is in generated IR file, but not in TBD file
<unknown>:0: error: please file a radar or open a bug on bugs.swift.org with this code, and add -Xfrontend -validate-tbd-against-ir=none to squash the errors
You can also reproduce this from the command-line:
@slavapestov I remember you said that TBDGen doesn't need to visit enum constructors because they don't have public visibility. So, I am wondering if we need to make TBD verification more tolerant in this case if these symbols shouldn't be in the TBD file, or should we add these symbols anyway?
Environment
Xcode 11.4.1 w/ Swift 5.3 snapshot (11th May 2020). macOS Catalina 10.15.4
Additional Detail from JIRA
md5: a0c53f290b235c9d6bb2cbd3addcb319
relates to:
Issue Description:
Reproducer (taken directly from SE-0280 proposal):
When building using Xcode, I get the following error:
You can also reproduce this from the command-line:
The text was updated successfully, but these errors were encountered: