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
[Diagnostics] Diagnose ambiguous solutions with warnings like regular ambiguities
If solutions either have no fixes at all or all of the are warnings,
let's use `diagnoseAmbiguity` to diagnose such cases as-if there are
no fixes at all.
Resolves: rdar://79657350
// expected-note@-2 {{use the 'withUnsafeMutableBytes' method on Array in order to explicitly convert argument to buffer pointer valid for a defined scope}}
202
202
203
203
// FIXME: This is currently ambiguous.
204
-
_ =OpaquePointer(&foo) // expected-error {{no exact matches in call to initializer}}
204
+
_ =OpaquePointer(&foo) // expected-error {{ambiguous use of 'init(_:)'}}
205
205
206
206
// FIXME: This is currently ambiguous.
207
-
_ =OpaquePointer(&arr) // expected-error {{no exact matches in call to initializer}}
207
+
_ =OpaquePointer(&arr) // expected-error {{ambiguous use of 'init(_:)'}}
208
208
209
209
_ =OpaquePointer(arr) // expected-warning {{initialization of 'OpaquePointer' results in a dangling pointer}}
210
210
// expected-note@-1 {{implicit argument conversion from '[Int]' to 'UnsafeRawPointer' produces a pointer valid only for the duration of the call to 'init(_:)'}}
0 commit comments