This seems to be caused by the `!` used in conjunction with a macro. Using the macro directly as condition does not exhibit this issue.
This seems to be caused by the `!` used in conjunction with a macro. Using the macro directly as condition does not exhibit this issue.