14 Mar
2024
14 Mar
'24
2:42 p.m.
On Thu Mar 14 14:41:12 2024 +0000, Yuxuan Shui wrote:
~~OK, this is getting too complex, too many work_items to chase down. I am going with the other option.~~
On second thought, this is completely fine. The work item created by `invoke_async_result` is not the one we free in `queue_cancel_item`. This also means `MFCancelWorkItem` is just not going to wait for the user callback _at all_. It waits for `scheduled_item_callback`/`periodic_item_callback`, etc., but those callbacks _**do not**_ call user callback directly.