This test regressed after recent changes

slavapestov · slavapestov · commit fc59abefe24a · 2016-06-18T17:15:26.000-07:00
We fail to emit a diagnostic here, because name lookup is able to find the
associated type, even though we don't build a valid generic signature in
this case.

Some more changes to name lookup to untangle "find members in protocols"
from "find concrete witness" flags are needed. I'll do this soon, as part
of fixing unqualified lookup of protocol typealiases, which currently
doesn't work either.
diff --git a/test/decl/ext/generic.swift b/test/decl/ext/generic.swift
@@ -152,4 +152,4 @@ struct S4<Q>: P4 {
   init(_: Q) { }
 }
 
-extension S4 where T : P5 {} // expected-error{{type 'T' in conformance requirement does not refer to a generic parameter or associated type}}
+extension S4 where T : P5 {} // expected-FIXME-error{{type 'T' in conformance requirement does not refer to a generic parameter or associated type}}

Original file line number	Diff line number	Diff line change
`@@ -152,4 +152,4 @@ struct S4<Q>: P4 {`
`152`	`152`	`init(_: Q) { }`
`153`	`153`	`}`
`154`	`154`
`155`		`-extension S4 where T : P5 {} // expected-error{{type 'T' in conformance requirement does not refer to a generic parameter or associated type}}`
	`155`	`+extension S4 where T : P5 {} // expected-FIXME-error{{type 'T' in conformance requirement does not refer to a generic parameter or associated type}}`