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
swift-driver version: 1.26.21 Apple Swift version 5.5.2 (swiftlang-1300.0.47.5 clang-1300.0.29.30)
Target: x86_64-apple-macosx12.0
Additional Detail from JIRA
Votes
0
Component/s
Compiler
Labels
Bug
Assignee
None
Priority
Medium
md5: 9072a5e40a5bbf5e1fa2d49f3bd2e507
Issue Description:
Consider the following:
publicprotocolTint{}extensionUIColor:Tint{}publicextensionTintwhere Self ==UIColor{staticvarhsRed:UIColor{.systemRed }}structModel{leta:(x:String, y:Tint)?letb:(x:String, y:Tint)?}// type of expression is ambiguous without more contextletm=Model(
a:(x:"", y:.hsRed),
b:(x:"", y:.hsRed))
This code unexpectedly fails to resolve the static member .hsRed, claiming the type is ambiguous (it isn't).
1. Prefixing both or any 1 of the .hsRed with an explicit UIColor resolves the issue.
2. Reducing the members of Model down from 2 to 1 resolves the issue.
3. Reducing the type of the members from a tuple down to a plain Tint? resolves the issue.
It appears there is some interplay happening, perhaps some kind of hierarchical exhaustion, where multiple members and tuple types combine to cause SE-0299 to fail.
The text was updated successfully, but these errors were encountered:
Environment
swift-driver version: 1.26.21 Apple Swift version 5.5.2 (swiftlang-1300.0.47.5 clang-1300.0.29.30)
Target: x86_64-apple-macosx12.0
Additional Detail from JIRA
md5: 9072a5e40a5bbf5e1fa2d49f3bd2e507
Issue Description:
Consider the following:
This code unexpectedly fails to resolve the static member
.hsRed
, claiming the type is ambiguous (it isn't).1. Prefixing both or any 1 of the
.hsRed
with an explicitUIColor
resolves the issue.2. Reducing the members of
Model
down from 2 to 1 resolves the issue.3. Reducing the type of the members from a tuple down to a plain
Tint?
resolves the issue.It appears there is some interplay happening, perhaps some kind of hierarchical exhaustion, where multiple members and tuple types combine to cause SE-0299 to fail.
The text was updated successfully, but these errors were encountered: