Simon Ser 7265a79e46 Drop "restrict" keyword ... The "restrict" keyword can be used to indicate that no other pointer will be used to access a chunk of memory while the restricted pointer is alive. If that promise is not upheld, undefined behavior is triggered. It may be difficult to ensure this property, and the property may be brittle - becoming invalid as code evolves. Just like "inline", let's just leave optimizations up to the compiler to figure out.		2026-05-25 08:42:35 +00:00
..
drm	Drop "restrict" keyword	2026-05-25 08:42:35 +00:00
session	Drop "restrict" keyword	2026-05-25 08:42:35 +00:00
headless.h	backend/headless: take wl_event_loop instead of wl_display	2024-01-25 15:05:36 +00:00
libinput.h	backend/libinput: guard against new enum entries	2026-02-13 09:41:02 -05:00
multi.h	backend/multi: take wl_event_loop instead of wl_display	2024-01-25 15:05:36 +00:00
wayland.h	backend/wayland: use a separate event queue for busy loops	2025-03-01 16:03:52 +00:00
x11.h	backend/x11: take wl_event_loop instead of wl_display	2024-01-25 15:05:36 +00:00