DartVM: factory allocation calls factory's constructor directly

[DartBot]

This issue was originally filed by kresten....@gmail.com

---

The following code should print "!", but it does not on current trunk of DartVM.

When doing new A(1,2), it jumps straight to invoke B(1,2) without using my factory method B.A(1,2). This only happens with DartVM -- frog and dartc gets it right. If B does not implement the A interface, then it calls the factory method allright.

---

interface A factory B {
  A(int x, int y);
}

class B implements A {
  final int x;
  final int y;
  B(this.x, this.y);
  factory A(int a, int b) { print("!"); return new B(a,b); }
}

main() {
   var v = new A(1,2);
}

[ghost]

DartVM is doing the right thing, this is a bug in dartc and frog.

The reason why factory A is not invoked at new A(..) is because B implements A. Without "implements A" factory A will be invoked when allocating A.

Assigning it to Peter so that he may provide more context/explanation.

[DartBot]

This comment was originally written by drfibonacci@google.com

---

Added Area-Compiler, Triaged labels.

[ghost]

I have filed issues 521 and 523 against dartc and frog.

[ghost]

Added Invalid label.