On Mon Jun 12 12:16:50 2023 +0000, Connor McAdams wrote:
Technically no, this _shouldn't_ happen. At one point I accidentally tested using an HUIAEVENT after it had already had `UiaRemoveEvent` called on it, and not checking this was causing it to segfault. Since that's technically undefined behavior, I guess having this check around is more confusing than helpful. I'll remove it then. Oh, wait, I thought this was in `advise_events`. In the `Release` method, this is more of a potential cleanup behavior. This should be released and set to NULL in `advise_events` when `advise_events` is called for removal. But if that doesn't occur for some reason and the entry is still around, we want to release it.
-- https://gitlab.winehq.org/wine/wine/-/merge_requests/2988#note_35448