-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Default interfaces] Debugger support #9556
Comments
@noahfalk @mikem8361 FYI |
To the list above I suggest adding:
Looking into the stepping issue I think you were accurate in predicting trouble at that spot. I filed dotnet/coreclr#22059 with my best guess on what in the code needs to be fixed. |
@tommcdon, could you please route this issue? Should be assigned to someone on your team? |
Historically teams that build new runtime features own the testing of those features across all the perpendiculars. I think its reasonable for the diagnostics team to assist with adding a new regression test, running it for you in the future + the general consulting/assistance we already did, but not to own this work item all up. |
Closing as the work to support default interfaces is done to the best of our knowledge |
This tracks checking whether we need any work on the debugger side to be able to invoke default interface methods and if any work is needed, this will track the work in question.
At minimum, we'll need:
The text was updated successfully, but these errors were encountered: