Optional Readonlyalternativesee ProcessKnownFunctionCallInput#alternativeArgsFrom
Optional ReadonlycfgOptional ReadonlyframeWhat this call lets the function around it reach about its own formals without naming one of them, e.g.
match.call() (ArgProp.Nse) or nargs() (ArgProp.Presence); see reflectiveRoles.
Optional ReadonlyhasOptional ReadonlykeepPropagate the out references produced by the arguments instead of dropping them.
Set this for functions that are transparent about their arguments, like (.
Optional Readonlykeepkeep the environment on the call vertex, for a later pass to look names up in
Optional ReadonlymarkMark the given arguments as evaluated in a data mask, like subset: their symbols may name columns of the
data instead of variables, while everything else in them is evaluated in the caller's frame as usual.
Optional ReadonlymarkMark the given arguments as non-standard-evaluated, like quote.
Optional Readonlypropsthe bitfield of CallProp
Optional ReadonlyreadOptional Readonlysigthe parameters and what each of their arguments is used for
Optional Readonlytagsthe array of SemanticCallTag
Optional Readonlytreatrecord mapping the actual function name called to the arguments that should be treated as function calls
Optional ReadonlyuseName that should be used for the origin (useful when needing to differentiate between functions like 'return' that use the default builtin processor)
Semantics of a built-in that hold no matter which processor handles the call. The remaining facts already have a home: the exit behavior in
cfg, whether flowR can fold the call in theevalHandlerof the definition, and the fallback for everything unmodelled inhasUnknownSideEffects.