You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Without testing, I think there's a latent bug in declare-event. The code is careful to avoid generating reads for pad fields in events when those have been declared with pad8 or pad16, but there's no corresponding avoidance for the pad32 type.
This came up in discussion with asvil on #lisp, who is implementing xkeyboard, which has pad fields in events.
The text was updated successfully, but these errors were encountered:
Without testing, I think there's a latent bug in declare-event. The code is careful to avoid generating reads for pad fields in events when those have been declared with pad8 or pad16, but there's no corresponding avoidance for the pad32 type.
This came up in discussion with asvil on #lisp, who is implementing xkeyboard, which has pad fields in events.
The text was updated successfully, but these errors were encountered: