From 0720157cd7d82db6c1efea615c2e78565b4ada0e Mon Sep 17 00:00:00 2001 From: Jason Zaugg Date: Tue, 2 Oct 2012 21:01:10 +0200 Subject: SI-6436 Handle ambiguous string processors Before, we got in an inifinite loop by chasing the error typed result of adaptToMemberWithArgs. One point of befuddlement remains: why did t6436 and t6436b behave differently before this change? --- test/files/neg/t6436b.scala | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 test/files/neg/t6436b.scala (limited to 'test/files/neg/t6436b.scala') diff --git a/test/files/neg/t6436b.scala b/test/files/neg/t6436b.scala new file mode 100644 index 0000000000..8023329e90 --- /dev/null +++ b/test/files/neg/t6436b.scala @@ -0,0 +1,9 @@ +object quasiquotes { + implicit def foo1(ctx: StringContext) = new { def q = ??? } + implicit def foo2(ctx: StringContext) = new { def q = ??? } +} + +object Test extends App { + import quasiquotes._ + println(StringContext("a").q()) +} -- cgit v1.2.3