Skip to content

[RuntimeAsync] Revisit TODOs in places of questionable intersections of existing scenarios and Async #115094

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

Open
Tracked by #109632
VSadov opened this issue Apr 27, 2025 · 2 comments

Comments

@VSadov
Copy link
Member

VSadov commented Apr 27, 2025

We have a number of scenarios that may or may not be reachable with Async methods, but right now do not have a well defined behavior if Async methods get there. A good example is COM interop.
Such scenarios are stubbed to throw exceptions and marked with // TODO: (async) revisit and examine if this needs to be supported

Some of these places may be truly unreachable, some may need to be made unreachable and in some cases we may need to provide some kind of support for Async.

This is the tracking issue to make sure that all these TODOs are revisited and removed after providing appropriate behavior.

@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Apr 27, 2025
Copy link
Contributor

Tagging subscribers to this area: @mangod9
See info in area-owners.md if you want to be subscribed.

Copy link
Contributor

Tagging subscribers to this area: @dotnet/interop-contrib
See info in area-owners.md if you want to be subscribed.

@agocke agocke added this to the 10.0.0 milestone May 19, 2025
@agocke agocke removed the untriaged New issue has not been triaged by the area owner label May 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

3 participants