Merged contraints lead to invalid type

[frabbit]

class Test {
 static function main() {
   var x: { foo: Int, bar: Int, ohno: Int } = merge({ foo: 1}, { bar: 2});
 }
 
 static function merge<A:{}, B:{}, C:A & B>(a:A, b:B):C {
  return null;
 }
}

[frabbit]

see: #9554 (comment)

[frabbit]

this is not really a bug, but it shows that this technique is not a replacement for returning A & B.

[Simn]

I suppose we really do need TIntersect or something to that extent...

[frabbit]

Ah, i just realized that & is just AExtend for AnonStatus, right?

[Simn]

Yes. Originally I thought that there should be a way to directly handle & when translating from syntax to typed expressions, but this falls apart when type parameters get involved (and probably in other situations as well).