Do not check for ambiguous implicits in viewExists

Previously `viewExists(X, Y)` failed if there were ambiguous
implicit conversions from X to Y. This is too fragile, as
demonstrated by test case run/array-addition.scala. Here,
the `genericArrayOps` implicit was not inserted because its
result type `Array[?T]` was deemed to be incompatible with
`? { +: : ? }`. It was incompatible because there were multiple
implicits that added :+ to arrays of various element types.
But once `genericArrayOps` gets applied, the type parameter
`?T` of the array result is fixed, and the ambuity goes away.

The scenario shows that we should not test for ambiguous implicits
in viewExists. Such a test is fragile because it depends on the
progress of type inference when the test is made. It's preferable
to just test for any implicit conversion to exist and to check
for ambiguities later, when the implicit conversion is actually
applied. This has also the potential of speeding up implicit search
in situations where `viewExists` is called often (e.g. when coupled
with overloading resolution).

2 files changed, 0 insertions, 0 deletions

diff --git a/tests/pending/run/array-addition.check b/tests/run/array-addition.check
index 7bfbd9c71..7bfbd9c71 100644
--- a/tests/pending/run/array-addition.check
+++ b/tests/run/array-addition.check
diff --git a/tests/pending/run/array-addition.scala b/tests/run/array-addition.scala
index 8def48e85..8def48e85 100644
--- a/tests/pending/run/array-addition.scala
+++ b/tests/run/array-addition.scala