aboutsummaryrefslogtreecommitdiff
path: root/modules
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-06-21 03:19:08 -0400
committerCraig Jennings <c@cjennings.net>2026-06-21 03:19:08 -0400
commit571da4996f84d96f6a8a73e6ca6844bfe2ca07ab (patch)
tree57dd1cfb4db739ef77c3b40902b6719c1913fc30 /modules
parent0805df5e6ac5aa4972600bbe3c01ec3d3c166592 (diff)
downloaddotemacs-571da4996f84d96f6a8a73e6ca6844bfe2ca07ab.tar.gz
dotemacs-571da4996f84d96f6a8a73e6ca6844bfe2ca07ab.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 'modules')
0 files changed, 0 insertions, 0 deletions