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

    Semantics of a built-in that hold no matter which processor handles the call.

    interface BuiltInFnInfo {
        ambient?: AmbientStateAccess | readonly AmbientStateAccess[];
        dispatches?: string[];
        frame?: number;
        hasUnknownSideEffects?: boolean | LinkTo<string | RegExp>;
        keepEnvironment?: boolean;
        props?: number;
        scope?: AmbientScope;
        sig?: FnSig;
        signals?: readonly string[];
        tags?: SemanticCallTags;
    }

    Hierarchy (View Summary)

    Index
    ambient?: AmbientStateAccess | readonly AmbientStateAccess[]

    how the call reads or writes global state like the graphics parameters, the options, or files, see AmbientStateAccess

    dispatches?: string[]

    the generics the call may dispatch to on (parts of) its arguments, like as.character for paste or format for the columns print shows of a data frame; any method of them may run

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

    hasUnknownSideEffects?: boolean | LinkTo<string | RegExp>
    keepEnvironment?: boolean

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

    props?: number

    the bitfield of CallProp

    scope?: AmbientScope

    the call changes that state for a scope only, see AmbientScope

    sig?: FnSig

    the parameters and what each of their arguments is used for

    signals?: readonly string[]

    The condition classes a call signals when every argument it is handed is a constant, like simpleError, error, and condition for stop("x").

    the array of SemanticCallTag