aboutsummaryrefslogtreecommitdiff
path: root/runtime/lua/vim/provider/python.lua
diff options
context:
space:
mode:
authorbfredl <bjorn.linse@gmail.com>2026-05-11 10:47:50 +0200
committerbfredl <bjorn.linse@gmail.com>2026-05-11 13:31:10 +0200
commit7e9015fecb4c65f84645f0257dbb8bab7b80effd (patch)
tree60af3e42fbc6cb86af950481550525bf38b9a181 /runtime/lua/vim/provider/python.lua
parent0e7d51a378173fdde0888dd9fd582aff0beb3d7e (diff)
downloadrneovim-7e9015fecb4c65f84645f0257dbb8bab7b80effd.tar.gz
rneovim-7e9015fecb4c65f84645f0257dbb8bab7b80effd.tar.bz2
rneovim-7e9015fecb4c65f84645f0257dbb8bab7b80effd.zip
fix(style): some clang-tidy 22 fixes
CI currently uses clang-tidy 20, but this affects local builds and CI is going to be upgraded sooner or later. Some remaining systematic issues: - clang-tidy warns agains any atoi() or atol() usage (because of no error handling) - functions which takes (char *fmt, char *only_string_arg) and expect fmt to contain exactly one "%s" usage. - error: initializing non-local variable with non-const expression depending on uninitialized non-local variable (cppcoreguidelines-interfaces-global-init) This is a much worse problem in C++ (hence C++ core guidelines) where initialization is intermingled with arbitrary code execution. I "think" in plain C, the linker will either resolve all these deterministically or barf an error. But with some restructuring we could make all static initialization actually static..
Diffstat (limited to 'runtime/lua/vim/provider/python.lua')
0 files changed, 0 insertions, 0 deletions