aboutsummaryrefslogtreecommitdiff
path: root/modules/custom-buffer-file.el
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
commitc52034d6712be46b3d96f420ec2ecff2ddb78f42 (patch)
tree99e19b311c0f21ec99e849d10f2036a4fa2a8ff7 /modules/custom-buffer-file.el
parent33418ed05d4030f817d0c8fcb3a669b80c5a827b (diff)
downloaddotemacs-c52034d6712be46b3d96f420ec2ecff2ddb78f42.tar.gz
dotemacs-c52034d6712be46b3d96f420ec2ecff2ddb78f42.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/custom-buffer-file.el')
0 files changed, 0 insertions, 0 deletions