-
Notifications
You must be signed in to change notification settings - Fork 4.7k
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Be consistent about caching behavior of function resolutions through IDynamicInterfaceCastable #107999
Labels
Milestone
Comments
dotnet-issue-labeler
bot
added
the
needs-area-label
An area label is needed to ensure this gets routed to the appropriate area owners
label
Sep 18, 2024
dotnet-policy-service
bot
added
the
untriaged
New issue has not been triaged by the area owner
label
Sep 18, 2024
We need to write some tests to validate that my thoughts on the caching behavior are correct, and then if I am right, we should be able to remove the special casing in NativeAOT cached interface dispatch path. |
Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas |
jkotas
removed
the
needs-area-label
An area label is needed to ensure this gets routed to the appropriate area owners
label
Sep 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Based on discussion in #106843 (comment) we need to validate the caching behavior here and not cause the runtimes to do variable amounts of work here.
The text was updated successfully, but these errors were encountered: