Fix argument validation in RuntimeType.InvokeMember#74998
Fix argument validation in RuntimeType.InvokeMember#74998stephentoub merged 1 commit intodotnet:mainfrom
Conversation
The rollout of `!!` erroneously moved an ArgumentNullException to be thrown earlier in the method, preventing a null name from being used (which is valid with BindingFlags.CreateInstance). (Separately, we should consider fixing the nullable reference type annotation on `string name`, since null is allowed in some circumstances.)
|
Tagging subscribers to this area: @dotnet/area-system-reflection Issue DetailsThe rollout of (Separately, we should consider fixing the nullable reference type annotation on Fixes #74977 (reply in thread)
|
|
Thanks @stephentoub. I assume we can also get this into 7.0 once it is in 8.0? |
|
That's my plan. |
|
/backport to release/7.0 |
|
Started backporting to release/7.0: https://github.com/dotnet/runtime/actions/runs/2980567108 |
The rollout of
!!erroneously moved an ArgumentNullException to be thrown earlier in the method, preventing a null name from being used (which is valid with BindingFlags.CreateInstance).(Separately, we should consider fixing the nullable reference type annotation on
string name, since null is allowed in some circumstances.)Fixes #74977 (reply in thread)
cc: @AaronRobinsonMSFT, @steveharter