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
headless	treewide: make type-check helpers take const pointers	2026-03-06 16:04:21 +08:00
libinput	backend/libinput: expose libinput context	2026-05-21 15:23:30 +00:00
multi	treewide: make type-check helpers take const pointers	2026-03-06 16:04:21 +08:00
session	Drop "restrict" keyword	2026-05-25 08:42:35 +00:00
wayland	treewide: make type-check helpers take const pointers	2026-03-06 16:04:21 +08:00
x11	wl_event_loop_add_fd: Only watch for READABLE & WRITABLE	2026-05-21 15:07:21 +00:00
backend.c	backend, output: send commit events after applying all in wlr_backend_commit()	2025-08-12 19:04:05 +02:00
meson.build	backend/session: make optional	2022-11-25 16:15:29 +00:00