Function useConfigForTest

Parameters

• config: {
      defaultEngine?: "r-shell" | "tree-sitter";
      engines?: readonly (undefined | {
          treeSitterWasmPath?: string;
          type?: "tree-sitter";
          wasmPath?: string;
      } | {
          rPath?: string;
          type?: "r-shell";
      })[];
      ignoreSourceCalls?: boolean;
      semantics?: {
          environment?: {
              overwriteBuiltIns?: {
                  definitions?: readonly (
                      | undefined
                      | {
                          assumePrimitive?: ...;
                          names?: ...;
                          suffixes?: ...;
                          type?: ...;
                      }
                      | {
                          assumePrimitive?: ...;
                          names?: ...;
                          type?: ...;
                          value?: ...;
                      }
                      | {
                          assumePrimitive?: ...;
                          config?: ...;
                          names?: ...;
                          processor?: ...;
                          type?: ...;
                      })[];
                  loadDefaults?: boolean;
              };
          };
      };
      solver?: {
          pointerTracking?: boolean;
          variables?: VariableResolve;
      };
  }

  • Optional ReadonlydefaultEngine?: "r-shell" | "tree-sitter"

    The default engine to use for interacting with R code. If this is undefined, an arbitrary engine from engines will be used.

  • Optional Readonlyengines?: readonly (undefined | {
        treeSitterWasmPath?: string;
        type?: "tree-sitter";
        wasmPath?: string;
    } | {
        rPath?: string;
        type?: "r-shell";
    })[]

    The engines to use for interacting with R code. Currently supports TreeSitterEngineConfig and RShellEngineConfig. An empty array means all available engines will be used.

  • Optional ReadonlyignoreSourceCalls?: boolean

    Whether source calls should be ignored, causing processSourceCall's behavior to be skipped

  • Optional Readonlysemantics?: {
        environment?: {
            overwriteBuiltIns?: {
                definitions?: readonly (
                    | undefined
                    | {
                        assumePrimitive?: ...;
                        names?: ...;
                        suffixes?: ...;
                        type?: ...;
                    }
                    | {
                        assumePrimitive?: ...;
                        names?: ...;
                        type?: ...;
                        value?: ...;
                    }
                    | {
                        assumePrimitive?: ...;
                        config?: ...;
                        names?: ...;
                        processor?: ...;
                        type?: ...;
                    })[];
                loadDefaults?: boolean;
            };
        };
    }

    Configure language semantics and how flowR handles them

    • Optional Readonlyenvironment?: {
          overwriteBuiltIns?: {
              definitions?: readonly (
                  | undefined
                  | {
                      assumePrimitive?: ...;
                      names?: ...;
                      suffixes?: ...;
                      type?: ...;
                  }
                  | {
                      assumePrimitive?: ...;
                      names?: ...;
                      type?: ...;
                      value?: ...;
                  }
                  | {
                      assumePrimitive?: ...;
                      config?: ...;
                      names?: ...;
                      processor?: ...;
                      type?: ...;
                  })[];
              loadDefaults?: boolean;
          };
      }

      Semantics regarding the handlings of the environment

      • Optional ReadonlyoverwriteBuiltIns?: {
            definitions?: readonly (
                | undefined
                | {
                    assumePrimitive?: ...;
                    names?: ...;
                    suffixes?: ...;
                    type?: ...;
                }
                | {
                    assumePrimitive?: ...;
                    names?: ...;
                    type?: ...;
                    value?: ...;
                }
                | {
                    assumePrimitive?: ...;
                    config?: ...;
                    names?: ...;
                    processor?: ...;
                    type?: ...;
                })[];
            loadDefaults?: boolean;
        }

        Do you want to overwrite (parts) of the builtin definition?

        • Optional Readonlydefinitions?: readonly (
              | undefined
              | {
                  assumePrimitive?: ...;
                  names?: ...;
                  suffixes?: ...;
                  type?: ...;
              }
              | {
                  assumePrimitive?: ...;
                  names?: ...;
                  type?: ...;
                  value?: ...;
              }
              | {
                  assumePrimitive?: ...;
                  config?: ...;
                  names?: ...;
                  processor?: ...;
                  type?: ...;
              })[]

          The definitions to load

        • Optional ReadonlyloadDefaults?: boolean

          Should the default configuration still be loaded?

  • Optional Readonlysolver?: {
        pointerTracking?: boolean;
        variables?: VariableResolve;
    }

    How to resolve constants, constraints, cells, ...

    • Optional ReadonlypointerTracking?: boolean

      Whether to track pointers in the dataflow graph, if not, the graph will be over-approximated wrt. containers and accesses

    • Optional Readonlyvariables?: VariableResolve

      How to resolve variables and their values