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
..
backend	Drop "restrict" keyword	2026-05-25 08:42:35 +00:00
interfaces	types/wlr_input_device: move init and finish function to private API	2022-03-07 16:37:41 +00:00
render	render/egl: disable implicit flush on context change	2026-05-21 14:58:02 -04:00
types	types/wlr_buffer: add buffer_get_drm_format helper function	2026-02-06 13:53:46 +00:00
util	util/rect_union: Limit rect_union_add to 1024 rects	2026-05-01 12:50:04 +00:00
wlr	backend/libinput: expose libinput context	2026-05-21 15:23:30 +00:00
xcursor	Add some missing includes/declarations	2023-06-05 21:06:19 +00:00
xwayland	treewide: make type-check helpers take const pointers	2026-03-06 16:04:21 +08:00
meson.build	render/color: add fallback stub when LCMS2 is disabled	2024-06-04 17:45:51 +00:00