@eagleoutice/flowr - v2.15.8
    Preparing search index...
    interface ProcessKnownFunctionCallInput<OtherInfo> {
        alternativeArgsFrom?: number;
        args: readonly (
            | "<>"
            | RExpressionList<OtherInfo & ParentInformation>
            | RFunctionDefinition<OtherInfo & ParentInformation>
            | RNamedFunctionCall<OtherInfo & ParentInformation>
            | RUnnamedFunctionCall<OtherInfo & ParentInformation>
            | RParameter<OtherInfo & ParentInformation>
            | RArgument<OtherInfo & ParentInformation>
            | RComment<OtherInfo & ParentInformation>
            | RLineDirective<OtherInfo & ParentInformation>
            | RForLoop<OtherInfo & ParentInformation>
            | RRepeatLoop<OtherInfo & ParentInformation>
            | RWhileLoop<OtherInfo & ParentInformation>
            | RIfThenElse<OtherInfo & ParentInformation>
            | RNamedAccess<OtherInfo & ParentInformation>
            | RIndexAccess<OtherInfo & ParentInformation>
            | RUnaryOp<OtherInfo & ParentInformation>
            | RBinaryOp<OtherInfo & ParentInformation>
            | RSymbol<OtherInfo & ParentInformation, Identifier>
            | RNumber<OtherInfo & ParentInformation>
            | RString<OtherInfo & ParentInformation>
            | RLogical<OtherInfo & ParentInformation>
            | RBreak<OtherInfo & ParentInformation>
            | RNext<OtherInfo & ParentInformation>
            | RPipe<OtherInfo & ParentInformation>
        )[];
        customControlFlow?: boolean;
        data: DataflowProcessorInformation<OtherInfo & ParentInformation>;
        hasUnknownSideEffect?: boolean;
        markAsNSE?: readonly number[];
        name: RSymbol<OtherInfo & ParentInformation>;
        nonFunction?: ReadonlySet<NodeId>;
        origin: BuiltInProcName | "default";
        patchData?: (
            data: DataflowProcessorInformation<OtherInfo & ParentInformation>,
            arg: number,
        ) => DataflowProcessorInformation<OtherInfo & ParentInformation>;
        reverseOrder?: boolean;
        rootId: NodeId;
        sig?: FnSig;
    }

    Type Parameters

    • OtherInfo
    Index
    alternativeArgsFrom?: number

    From this argument index on, the arguments are alternatives of which at most one is evaluated, which is how switch picks an arm. The arguments before it are evaluated in order as usual.

    The arguments to the function call.

    customControlFlow?: boolean

    Suppress the default control flow linkage (arguments in order, then the call). Constructs that branch or loop set this and wire their control flow themselves.

    The dataflow processor information at the point of the function call.

    hasUnknownSideEffect?: boolean

    Does the call have a side effect that we do not know a lot about which may have further consequences?

    markAsNSE?: readonly number[]

    which arguments are reevaluated, like a loop body

    The name of the function being called.

    nonFunction?: ReadonlySet<NodeId>

    see ProcessAllArgumentInput#nonFunction

    origin: BuiltInProcName | "default"

    The origin to use for the function being called.

    allows passing a data processor in-between each argument

    reverseOrder?: boolean

    should arguments be processed from right to left? This does not affect the order recorded in the call but of the environments

    rootId: NodeId

    The node ID to use for the function call vertex.

    sig?: FnSig

    the signature of the called function, the one place stating which arguments it evaluates