aboutsummaryrefslogtreecommitdiff
path: root/docs/specs/debug-profiling-spec.org
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
commita249e415c7199e3d4698f1956687fa351296a357 (patch)
treebdc9efadba60e08a43a5f687110fe12651172525 /docs/specs/debug-profiling-spec.org
parenta8571effadacd6f94291bfd57b7e58900a2e5816 (diff)
downloaddotemacs-a249e415c7199e3d4698f1956687fa351296a357.tar.gz
dotemacs-a249e415c7199e3d4698f1956687fa351296a357.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 'docs/specs/debug-profiling-spec.org')
0 files changed, 0 insertions, 0 deletions