Reflection: Easier reflection for known members

[FelixKlakow]

There are still no better way in C# for doing reflection for known Public members than the usual methods found among the API.
Sometimes this is pain to work with as it's unclear during compile time if you maybe got none or the wrong member. I suggest that we should be able to do things like this:

static readonly MethodInfo MyMethod = reflect(Enumerable.Average(IEnumerable<decimal>));
static readonly MethodInfo MyMethod = reflect(Enumerable.Average(IEnumerable<object>)); // Compile time error as it doesn't exist
static readonly PropertyInfo MyProperty = reflect(MyType.MyProperty);

[YairHalberstadt]

This has been discussed previously at #712

See also this blog post about why it's never gained much traction: https://docs.microsoft.com/en-gb/archive/blogs/ericlippert/in-foof-we-trust-a-dialogue

[FelixKlakow]

Sad, this is still definitely a feature a lot of people want when working a lot with reflection.

[YairHalberstadt]

Definitely, but it's never quite happened.

I imagine that if somebody were to do all the legwork of speccing and implementing it, then it would have a decent chance of being accepted, but that's a significant amount of work.

[HaloFour]

This is something that can be provided by tooling. For example an analyzer could inspect the use of reflection APIs and compare it to the types being reflected and provide warnings. IntelliJ does this with Java, for instance: