{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 一纸荒年 Trace。 的问题《Is there any reason why .NET's Reflection API》','https://www.manongdao.com/q-1128001.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
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"?
相关问题
- Generic Generics in Managed C++
- How to Debug/Register a Permanent WMI Event Which
- C# how to invoke a field initializer using reflect
- 'System.Threading.ThreadAbortException' in
- Bulk update SQL Server C#
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)