Refactor fire_and_forget methods in AppLogic to use weak refs #6295
Labels
Area-CodeHealth
Issues related to code cleanliness, linting, rules, warnings, errors, static analysis, etc.
Issue-Task
It's a feature request, but it doesn't really need a major design.
Needs-Tag-Fix
Doesn't match tag requirements
Product-Terminal
The new Windows Terminal.
Milestone
...
AppLogic
controls the lifetime of the entire application, so it's actually never going away, and we don't need to really worry about it. Though...it wouldn't hurt to do the right thing there as well.Originally posted by @zadjii-msft in https://github.com/_render_node/MDI0OlB1bGxSZXF1ZXN0UmV2aWV3Q29tbWVudDQzMzQyMzM1NQ==/comments/review_comment
Basically, there's a small handful of
fire_and_forget
methods inAppLogic
that could be refactored to use the weak reference pattern mentioned in the aboveThe text was updated successfully, but these errors were encountered: