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

    Interface DefaultBuiltInProcessorConfiguration

    interface DefaultBuiltInProcessorConfiguration {
        cfg?: ExitPointType;
        forceArgs?: "all" | readonly boolean[];
        hasUnknownSideEffects?: boolean | LinkTo<string | RegExp>;
        keepArgumentOut?: boolean;
        markArgsAsNSE?: NseArguments;
        readAllArguments?: boolean;
        returnsNthArgument?: number | "last";
        treatAsFnCall?: Record<string, readonly string[]>;
        useAsProcessor?: BuiltInProcName;
    }

    Hierarchy (View Summary)

    Hierarchy-Diagram

    UML class diagram of DefaultBuiltInProcessorConfiguration
    Index

    Properties

    cfg? forceArgs? hasUnknownSideEffects? keepArgumentOut? markArgsAsNSE? readAllArguments? returnsNthArgument? treatAsFnCall? useAsProcessor?

    Properties

    cfg?: ExitPointType
    forceArgs?: "all" | readonly boolean[]

    which of the arguments should be forced? this may be all, e.g., if the function itself is unknown on encounter

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

    Propagate the out references produced by the arguments instead of dropping them. Set this for functions that are transparent about their arguments, like (.

    markArgsAsNSE?: NseArguments

    Mark the given arguments as non-standard-evaluated, like quote.

    readAllArguments?: boolean
    returnsNthArgument?: number | "last"
    treatAsFnCall?: Record<string, readonly string[]>

    record mapping the actual function name called to the arguments that should be treated as function calls

    useAsProcessor?: BuiltInProcName

    Name that should be used for the origin (useful when needing to differentiate between functions like 'return' that use the default builtin processor)

    Settings

    Member Visibility

    On This Page

    Properties