vasilito
cb424d7448
verify-patch-sanity.py validates every active recipe .patch has internally- consistent hunk line counts — catching the 'malformed patch at line N' failure at commit/CI/preflight time instead of hours into a cook. This cycle hit that class three times (qtwaylandscanner, sddm, xwayland), each only discovered when cookbook tried to apply the patch. Running it across the repo found 29 latent malformed patches (validated against GNU patch: e.g. relibc/P3-sysv-ipc reproduces 'malformed patch at line 22'). They were harmless only because they sit in vendored recipes (baked, not re- applied) — but would fail on any version-bump re-derivation. --fix recounts the hunk headers (body untouched) and repaired all 29. Wired into build-preflight.sh (Phase 1.0D) and redbear-ci.yml, with a unit test (test-patch-sanity.sh). Skips archived/legacy trees and unvalidatable formats (empty placeholders, bare-@@ git hunks).
40 lines
912 B
C++
40 lines
912 B
C++
// RUN: %clang_cc1 -verify %s
|
|
|
|
// FIXME: We could in principle support cases like this (particularly, cases
|
|
// where the statement-expression contains no labels).
|
|
template <typename... T> void f1() {
|
|
int arr[] = {
|
|
({
|
|
T(); // expected-error {{unexpanded parameter pack}}
|
|
}) ... // expected-error {{does not contain any unexpanded parameter packs}}
|
|
};
|
|
}
|
|
|
|
// FIXME: The error for this isn't ideal; it'd be preferable to say that pack
|
|
// expansion of a statement expression is not permitted.
|
|
template <typename... T> void f2() {
|
|
[] {
|
|
int arr[] = {
|
|
T() + ({
|
|
foo:
|
|
T t; // expected-error {{unexpanded parameter pack}}
|
|
goto foo;
|
|
0;
|
|
}) ...
|
|
};
|
|
};
|
|
}
|
|
|
|
template <typename... T> void f3() {
|
|
({
|
|
int arr[] = {
|
|
[] {
|
|
foo:
|
|
T t; // OK, expanded within compound statement
|
|
goto foo;
|
|
return 0;
|
|
} ...
|
|
};
|
|
});
|
|
}
|