fix: Fix resolveNamedType cannot resolve type parameter in contextual element

[HerrCai0907]

fix: #2447 and #2446

• I've read the contributing guidelines
• I've added my name and email to the NOTICE file

[dcodeIO]

This looks like there is a foregoing issue, as ctxTypes should have all the types. Is there perhaps something missing instead where ctxTypes is populated? Like, right now, lookupGenericType does after-the-fact what should already have been done before it seems.

[HerrCai0907]

Yes, we just need to find a position to sync generic type in ctxElement to ctxType when ctxElement is Function or Class.

[dcodeIO]

This is somewhat similar. The actualFunction should be an instance of prototype, then sharing state, or is it different?

[HerrCai0907]

actualFunction is caller side context. But inferring default type, it need callee side context.

[HerrCai0907]

class F<T> {
  foo(a: StaticArray<string>): string[] {
    const result = a.slice(0);
    // push some things onto "result"
    return result;
  }
}
export function foo(a: StaticArray<string>): string[] {
  let f = new F<f64>();
  return f.foo(a)
}

consider this case. In old version, generic T in class F will pass through contextualTypeArguments and cause error.

[dcodeIO]

I think I see now. Can you add a comment along the lines of...?

// Default parameters are resolved in context of the called function, not the calling function

[MaxGraey]

Thanks!