DartVM: type name shadowed with a type variable should not be available in a static context?

[DartBot]

This issue was originally filed by ief...@unipro.ru

---

What steps will reproduce the problem?
Run the following test:

class C {}
class G<C> {
  static f() => new C();
}

main() {
  try {
    G.f();
  } catch(var x){}
}

What is the expected output? What do you see instead?
Expected: compile-time error? (I'm not 100% sure that I deduced this from the spec correctly. Probably, the spec may be clearer about this).

Actual: successful completion.

What version of the product are you using? On what operating system?
DartVM r5705

[anders-sandholm]

Added Area-VM, Triaged labels.

[DartBot]

This comment was originally written by zundel@google.com

---

I'm pretty sure this is not valid as a compile-time error, as C is not in scope in the static method 'f', it should resolve through to class 'C'.

[iposva-google]

Regis, can you verify the validity of this bug?

---

Set owner to @crelier.
Added Accepted label.

[crelier]

From the spec:
"The type parameters of a generic declaration G are in scope in the bounds of all of the type parameters of G. The type parameters of a generic class or interface declaration G are also in scope in the extends and implements clauses of G (if these exist) and in the non-static members of G."

It follows that the type parameters are not in scope in the static members of G. Therefore, class C above is not shadowed by the type parameter C. No compile-time error should be reported and the VM is doing the right thing.

---

Added AsDesigned label.

[crelier]

Added Duplicate label.
Marked as being merged into #2629.