-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Remove DelegateInvokeStubManager
#88683
Remove DelegateInvokeStubManager
#88683
Conversation
All Delegate Invoke scenarios now use the StubLinker. This means there is an inherent confusion between the two stub managers. Upon further inspection combining these two by adding a new flag on the Stub class means they can be combined logically and simplify the code path by removing a StubManager.
Tagging subscribers to this area: @tommcdon Issue DetailsAll Delegate Invoke scenarios now use the #Fixes 85339
|
/cc @dotnet/dotnet-diag |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
The failures are known. I reran the tests before checking for known issues. |
All Delegate Invoke scenarios now use the
StubLinker
. This means there is an inherent confusion between the two stub managers. Upon further inspection combining these two by adding a new flag on theStub
class means they can be combined logically and simplify the code path by removing aStubManager
.Fixes #85339