libinput/.clang-tidy

# optin.core.unix.Malloc: disabled so we can use __attribute__((cleanup)) without leak complaints
# optin.core.EnumCastOutOfRange: disabled because we use a lot of "wrong" enum values for testing
#                                and internally and don't want those values leak into the public API
Checks: >
  -clang-analyzer-unix.Malloc,
  -clang-analyzer-optin.core.EnumCastOutOfRange
WarningsAsErrors: '*'
util: add various helper functions to use __attribute__(cleanup) Taken from libei, with slight modifications. The general approach is: basic data types use _autofoo_ to call the maching foo function on cleanup. Struct types use _unref_, _destory_, _free_, whichever applies to that struct. Notably: attribute syntax depends on where it's declared [1] so in the following examles only a, b, and d have the autofree attribute: _autofree_ char a, b; char c, _autofree d; Simplest way to ensure it's all correct to keep the declarations one per line. [1] https://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html#Attribute-Syntax Part-of: <https://gitlab.freedesktop.org/libinput/libinput/-/merge_requests/1184> 2025-04-01 11:25:58 +10:00			`# optin.core.unix.Malloc: disabled so we can use __attribute__((cleanup)) without leak complaints`
Add a clang-tidy file This gives us the ninja clang-tidy command. clang-tidy replaces scan-build and is more featureful (and picky). Part-of: <https://gitlab.freedesktop.org/libinput/libinput/-/merge_requests/1182> 2025-04-03 13:25:51 +10:00			`# optin.core.EnumCastOutOfRange: disabled because we use a lot of "wrong" enum values for testing`
			`# and internally and don't want those values leak into the public API`
			`Checks: >`
util: add various helper functions to use __attribute__(cleanup) Taken from libei, with slight modifications. The general approach is: basic data types use _autofoo_ to call the maching foo function on cleanup. Struct types use _unref_, _destory_, _free_, whichever applies to that struct. Notably: attribute syntax depends on where it's declared [1] so in the following examles only a, b, and d have the autofree attribute: _autofree_ char a, b; char c, _autofree d; Simplest way to ensure it's all correct to keep the declarations one per line. [1] https://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html#Attribute-Syntax Part-of: <https://gitlab.freedesktop.org/libinput/libinput/-/merge_requests/1184> 2025-04-01 11:25:58 +10:00			`-clang-analyzer-unix.Malloc,`
Add a clang-tidy file This gives us the ninja clang-tidy command. clang-tidy replaces scan-build and is more featureful (and picky). Part-of: <https://gitlab.freedesktop.org/libinput/libinput/-/merge_requests/1182> 2025-04-03 13:25:51 +10:00			`-clang-analyzer-optin.core.EnumCastOutOfRange`
clang-tidy: fix WarningAsErrors option to actually work Not a boolean, despite what one would immediately assume. Closes #1168 Part-of: <https://gitlab.freedesktop.org/libinput/libinput/-/merge_requests/1298> 2025-08-11 14:49:16 +10:00			`WarningsAsErrors: '*'`