Home/ Questions/Q 6047893
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-23T07:24:09+00:00

Is there any reason why .NET’s Reflection API uses arrays instead of indexers to

  • 0

Is there any reason why .NET’s Reflection API uses arrays instead of indexers to access a type’s members/methods/properties/etc.? I understand the overhead of adding collection objects classes such as MemberInfoCollection, MethodInfoCollection, etc. However, these collection objects classes could be created instantiated on demand. Was the design rationale something other than just “dissuade programmers from using Reflection unless they really need it”?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    These APIs were created in .Net 1.0, which didn’t have generics.

    They couldn’t just return a ReadOnlyCollection<MemberInfo>, and they were too lazy to create a separate typed collection class for each type they need to return.

    (I don’t have a source for this belief)

    • 0