aya/clippy.sh

#!/usr/bin/env sh

# `-C panic=abort` because "unwinding panics are not supported without std";
# integration-ebpf contains `#[no_std]` binaries.
#
# `-Zpanic_abort_tests` because "building tests with panic=abort is not supported without
# `-Zpanic_abort_tests`"; Cargo does this automatically when panic=abort is set via profile
# but we want to preserve unwinding at runtime - here we are just running clippy so we don't
# care about unwinding behavior.
#
# `+nightly` because "the option `Z` is only accepted on the nightly compiler".
exec cargo +nightly hack clippy "$@" --all-targets --feature-powerset --workspace -- --deny warnings -C panic=abort -Zpanic_abort_tests
Enable unwinding in userspace Unwinding gives us more information, so we shouldn't disable it globally. It is already disabled for BPF targets via the target configs in rustc itself. This complicates the clippy invocation somewhat, so put it in a shell script for developer as well as CI use. 2 months ago			`#!/usr/bin/env sh`

			# `-C panic=abort` because "unwinding panics are not supported without std";
			# integration-ebpf contains `#[no_std]` binaries.
			`#`
			# `-Zpanic_abort_tests` because "building tests with panic=abort is not supported without
			# `-Zpanic_abort_tests`"; Cargo does this automatically when panic=abort is set via profile
			`# but we want to preserve unwinding at runtime - here we are just running clippy so we don't`
			`# care about unwinding behavior.`
			`#`
			# `+nightly` because "the option `Z` is only accepted on the nightly compiler".
			`exec cargo +nightly hack clippy "$@" --all-targets --feature-powerset --workspace -- --deny warnings -C panic=abort -Zpanic_abort_tests`