I am trying to call the function `function`
to define a function in R code.
As we all know™️, `function`
is a .Primitive
that’s
After digging a little bit through the source code, here are a few observations:
The actual function creation is done by mkCLOSXP(). This is what gets called by function() {}
, by as.function.default()
and by .Primitive("function")
(a.k.a. `function`
)
as.function.default()
gets routed to do_asfunction(), which also calls CheckFormals(). However, it directly constructs these formals a few lines above that.
As you pointed out, the other place where CheckFormals()
gets called is inside do_function()
. However, I don't think do_function()
gets called by anything other than .Primitive("function")
, so this is the only situation where CheckFormals()
is called on the user's input.
CheckFormals()
does actually correctly validate a pairlist
object.
You can check the last point yourself by running parts of the CheckFormals()
function using inline::cfunction
inline::cfunction( c(x="ANY"),
'Rprintf("is list?: %d\\nTag1 OK?: %d\\nTag2 OK?: %d\\nTag3 NULL?: %d\\n",
isList(x), TYPEOF(TAG(x)) == SYMSXP, TYPEOF(TAG(CDR(x))) == SYMSXP,
CDR(CDR(x)) == R_NilValue); return R_NilValue;' )( formals(mean) )
# is list?: 1
# Tag1 OK?: 1
# Tag2 OK?: 1
# Tag3 NULL?: 1
So, somewhere between you passing formals(means)
to .Primitive("function")
and it getting forwarded to CheckFormals()
by do_function()
, the argument loses its validity. (I don't know the R source well enough to tell you how that happens.) However, since do_function()
is only called by .Primitive("function")
, you don't encounter this situation with any other examples.