diff options
| author | Craig Jennings <c@cjennings.net> | 2026-06-21 03:19:08 -0400 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-06-21 03:19:08 -0400 |
| commit | 0aa85dd219f4be8dbf3383661fd2b42370945b87 (patch) | |
| tree | 0ba557d43691666ad181c6ec3718a7d5e2a0cdee /scripts/theme-studio/build-theme.el | |
| parent | 4a8c572ba6a64be997be072b44ef5ff62674d820 (diff) | |
| download | dotemacs-0aa85dd219f4be8dbf3383661fd2b42370945b87.tar.gz dotemacs-0aa85dd219f4be8dbf3383661fd2b42370945b87.zip | |
test: make subr mocks variadic for native-comp, add arity meta-test
Re-enabling native-comp surfaced a suite-wide fragility. When a test redefines a C primitive (or a native-compiled function), native-comp routes native callers through a trampoline that calls the mock with the primitive's maximum arity. A fixed-arity mock narrower than the primitive then throws wrong-number-of-arguments, intermittently, as the eln-cache fills.
I swept every arity-narrow subr mock to append &rest _ (188 sites, preserving any named args the body uses), and added tests/test-meta-subr-mock-arity.el, which fails make test on any subr mock too narrow for the primitive's arity. The rule isn't "never mock a subr". The suite mocks message and completing-read freely. It's "a subr mock must accept the primitive's arity."
Background, the three failure modes, and the research are in docs/native-comp-subr-mocking.org.
Diffstat (limited to 'scripts/theme-studio/build-theme.el')
0 files changed, 0 insertions, 0 deletions
