You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Given ConstructorInfo has an Invoke method, why not have a CreateDelegate method, so I can invoke it in a type-safe manner, without boxing and object[] allocation?
Original Comments
Fiona Niu[MSFT] on 10/28/2018, 11:03 PM:
Thank you for taking the time to provide your suggestion. We will do some preliminary checks to make sure we can proceed further. You will hear from us in about a week on our next steps.
The text was updated successfully, but these errors were encountered:
A constructor on a type is really a void-returning instance method, but presumably if you want to wrap a constructor within a delegate you actually wanted to instantiate the object, returning the new object instance. This isn't something that can be accomplished with a single method invocation. See #32520 for an alternative proposal which attempts to provide a usable API for this scenario.
This issue has been moved from a ticket on Developer Community.
Given ConstructorInfo has an Invoke method, why not have a CreateDelegate method, so I can invoke it in a type-safe manner, without boxing and object[] allocation?
Original Comments
Fiona Niu[MSFT] on 10/28/2018, 11:03 PM:
Thank you for taking the time to provide your suggestion. We will do some preliminary checks to make sure we can proceed further. You will hear from us in about a week on our next steps.
The text was updated successfully, but these errors were encountered: