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

    Everything flowR knows about one function, no matter which of its sources knows it; see fnInfo. It extends BuiltInFnInfo, so anything taking what a built-in states takes this as well.

    interface FnInfo {
        builtIn: boolean;
        entry?: DecodedFunction;
        foldable: boolean;
        frame?: number;
        keepEnvironment?: boolean;
        name: Identifier;
        package?: string;
        parameters: readonly string[];
        props?: number;
        sig?: FnSig;
        tags?: SemanticCallTags;
        version?: string;
    }

    Hierarchy (View Summary)

    Index
    builtIn: boolean

    whether flowR's own built-in definitions state anything about the name

    Optional Readonlyentry

    the signature database entry: where the function is defined, its callees, its help topic

    foldable: boolean

    whether flowR's value solver can fold a call of it to a constant

    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

    the identifier the answer is for, with the namespace filled in when an unqualified ask resolved to a package

    package?: string

    the package the answer is for, undefined when the name resolves to no package at all

    parameters: readonly string[]

    the formal names in order, empty when neither source declares any

    props?: number

    the bitfield of CallProp

    sig?: FnSig

    the parameters and what each of their arguments is used for

    the array of SemanticCallTag

    version?: string

    the package version the answer is for, i.e. the one the analysis assumes; see SignatureDb.versionOf