@eagleoutice/flowr - v2.15.8
    Preparing search index...

    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 the evalHandler of the definition, and the fallback for everything unmodelled in hasUnknownSideEffects.

    interface BuiltInFnInfo {
        frame?: number;
        keepEnvironment?: boolean;
        props?: number;
        sig?: FnSig;
        tags?: SemanticCallTags;
    }

    Hierarchy (View Summary)

    Index
    frame?: number

    What 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.

    keepEnvironment?: boolean

    keep the environment on the call vertex, for a later pass to look names up in

    props?: number

    the bitfield of CallProp

    sig?: FnSig

    the parameters and what each of their arguments is used for

    the array of SemanticCallTag