AI are usually very circumspect. But they were pretty much unanimous saying "programmers know what NOOP (or NOP) is, and this is industry-wide (e.g. jQuery.noop). The hyphen is noise, and if someone didn't know what 'noop' was they'd learn it quickly. Once they learned they would find the hyphen unnecessary."
I was motivated to finally pull the trigger on this due to the new rules for HIJACK. You can use NOOP here as a placeholder, just long enough to get a new identity... then use that identity in a derivation for the function you're going to hijack with.
Example:
let /panic-old: hijack panic/ noop/
hijack panic/ adapt panic-old/ [
print "PANIC ACTION! is being triggered from a usermode call"
print mold reason
;
; ...adaptation falls through to our copy of the original PANIC
]
Maybe a better placeholder would be some kind of UNREACHABLE that errors when called... if you forgot to fill it in. But, NOOP is at least not the worst choice.
(Actually, it occurs to me that if you could HIJACK with VOID, it could just leave the stub as a dummy... and then completely overwrite it with the subsequent HIJACK and just give back NULL to say nothing was there...thus not allocating anything extra. That's probably best.)