co19_2/LanguageFeatures/Instantiate-to-bound/nonfunction_typedef/dynamic/nonfunction_l2_t05 expectation

[eernstg]

Said test expects the raw type A to be A<B<dynamic, dynamic>, B<dynamic, dynamic>>, but it should actually be B<B<dynamic, dynamic>, dynamic>. The reason for this is that the instantiation-to-bound algorithm breaks a loop (here: X1 andX2) by replacing all the variables in the loop in one step.

(OK, it's hard to tell whether A or B is the right way to spell B here, but comparison A<T1, T2> and B<T1, T2> for equality should yield true in any case, so that shouldn't matter).

In any case, the expectation should be adjusted, and using A<B<dynamic, dynamic>, dynamic> would presumably be a reasonable expectation, testing at the same time that A and B have the expected equality.