Add a couple fixes to generic method invocation

[daxian-dbw]

PR Summary

Fix #16809
Follow up on #12412

Add a couple fixes to generic method invocation:

1. For a generic type argument, if it doesn't exist at compilation time but available at run time, it should work as expected.
2. For a generic type argument, if it doesn't exist at all, we should report error about which type name cannot be resolved.
3. Make sure the tests actually run and fix all the tests.

@vexx32 It turns out the tests you added didn't run at all because of this:

PowerShell/test/powershell/Language/Parser/MethodInvocation.Tests.ps1

Lines 3 to 5 in 8af0834

	if ( $IsCoreCLR ) {
	return
	}

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • None
  • OR
  • Experimental feature(s) needed
    • Experimental feature name(s):
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    • Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.

[vexx32]

🤦 Can't believe I didn't catch that... does that mean none of the tests in that file were running, then? Glad you caught that!

The changes here look good to me on the surface, thanks for adding this in! 💖

[pull-request-quantifier-deprecated]

This PR has 252 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Large
Size       : +132 -120
Percentile : 65.2%

Total files changed: 5

Change summary by file extension:
.cs : +59 -51
.resx : +0 -3
.ps1 : +73 -66

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detetcted.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

[SeeminglyScience]

2. For a generic type argument, if it doesn't exist at all, we should report error about which type name cannot be resolved.

What about generic constraint violations? e.g.

[enum]::GetName[object]([object]::new())

Calling MakeGenericMethod([object]) throws this error message:

GenericArguments[0], 'System.Object', on 'System.String GetName[TEnum](TEnum)' violates the constraint of type 'TEnum'.

Is that surfaced?

[daxian-dbw]

Is that surfaced?

Sorta :) The error message still has room to improve, for example, list out the specified type parameters (which may be too long to make the message less readable).

[SeeminglyScience]

Sorta :) The error message still has room to improve, for example, list out the specified type parameters (which may be too long to make the message less readable).

I was expecting the generic method not found message so I'll take it! 😁