Skip to content
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-15260] Calling .init(...) instead of TypeName(...) for double parameter type inference for number literals fail to infer type as Double #57582

Open
mattyoung opened this issue Sep 29, 2021 · 0 comments
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior.

Comments

@mattyoung
Copy link

Previous ID SR-15260
Radar None
Original Reporter @mattyoung
Type Bug
Environment

Xcode Version 13.0 (13A233)

Additional Detail from JIRA
Votes 0
Component/s
Labels Bug
Assignee None
Priority Medium

md5: 5b17b186005d9d978e5d99706c962020

Issue Description:

struct S {
    init(_ v: Double) {}
}
func foo(_ v: S) {}
func bar(_ v: [S]) {}
let s: S = .init(1/2)   // ok
foo(.init(1/2))         // ok
bar([S(1/2)])           // ok
bar([.init(1/2)]) // Cannot convert value of type 'Int' to expected argument type 'Double'

See: https://forums.swift.org/t/why-calling-swiftui-color-redblue-compiler-can-infer-param-type-is-double-but-calling-with-init-redblue-alpha-it-cannot-and-must-use-explicit-double-literal/52427/2

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior.
Projects
None yet
Development

No branches or pull requests

1 participant