code wiki / probe

topic: probe

23 modules sharing the probe name family (derived from the tree's prefix discipline).

moduledescriptionlinesfuncs
_probe_alw2.nxprobe10
_probe_mulpow2_guard.nxAdversarial probe: reproduce the EXACT log2-by-halving + k<W guard logic from764
_probe_mulpow2_soundness.nxAdversarial probe #2: is the LIVE rule's union actually SOUND for every k it794
nx_probe.nxon-device capability fingerprint with vendor-claim39712
nx_probe_arity_live.nxLIVE WITNESS for the in-compiler call-arity check (radar evidence 2026-08-05).132
nx_probe_castmut2_live.nxDISCRIMINATOR (2026-08-05): is the cast-mutation PER-VALUE or check-wide?163
nx_probe_castmut_live.nxRESIDUE EXPERIMENT (2026-08-05, climb v4 rung 1): does `b as i64` in183
nx_probe_ctor.nxbisect the tagged-enum SIGSEGV: does the CONSTRUCTOR alone131
nx_probe_dym_ident_live.nxLIVE WITNESS for IDENTIFIER DID-YOU-MEAN (2026-08-05).181
nx_probe_dym_live.nxLIVE WITNESS for DID-YOU-MEAN (2026-08-05). A misspelled call must be172
nx_probe_dym_type_live.nxLIVE WITNESS for TYPE-NAME DID-YOU-MEAN (2026-08-05).191
nx_probe_exhaust_live.nxPROBE (2026-08-05): does nx_cc check MATCH EXHAUSTIVENESS?262
nx_probe_float.nxEVIDENCE GATE for the disputed "no native f32/f64,141
nx_probe_intptr_live.nxLIVE WITNESS for the REVERSE call-arg type direction (2026-08-05):212
nx_probe_match.nxEVIDENCE GATE for the disputed "exhaustive match342
nx_probe_match_nobind.nxbisect: does match DISPATCH on a tagged enum work131
nx_probe_match_plain.nxisolate: does PLAIN-enum match (no payload)161
nx_probe_multierr_live.nxLIVE WITNESS for MULTI-ERROR RECOVERY (2026-08-05). One broken173
nx_probe_pid.nx92
nx_probe_ptrarg_live.nxLIVE WITNESS for pointer-vs-scalar param type checking (2026-08-05).152
nx_probe_ptrint_live.nxLIVE WITNESS for the ENFORCED param-type direction (2026-08-05):142
nx_probe_test.nxsmoke for nx_probe SA-1 MVP.991
probe_blob_journal.nx591