Interface DefaultBuiltInProcessorConfiguration
interface DefaultBuiltInProcessorConfiguration {
cfg?: ExitPointType;
forceArgs?: "all" | readonly boolean[];
hasUnknownSideEffects?: boolean | LinkTo<string | RegExp>;
readAllArguments?: boolean;
returnsNthArgument?: number | "last";
}
cfg?: ExitPointType;
forceArgs?: "all" | readonly boolean[];
hasUnknownSideEffects?: boolean | LinkTo<string | RegExp>;
readAllArguments?: boolean;
returnsNthArgument?: number | "last";
}
Hierarchy (view full)
- ForceArguments
- DefaultBuiltInProcessorConfiguration
Hierarchy-Diagram
Index
Settings
Member Visibility
On This Page
- src
- util
- abstract-interpretation
- benchmark
- stats
- summarizer
- first-phase
- second-phase
- data.ts
- summarizer.ts
- slicer.ts
- stopwatch.ts
- cli
- common
- repl
- commands
- server
- core.ts
- execute.ts
- print-version.ts
- prompt.ts
- script-core
- benchmark-app.ts
- benchmark-helper-app.ts
- export-quads-app.ts
- flowr.ts
- flowr-main-options.ts
- run-script.ts
- slicer-app.ts
- statistics-app.ts
- statistics-helper-app.ts
- summarizer-app.ts
- core
- dataflow
- environments
- graph
- dataflowgraph-builder.ts
- diff.ts
- edge.ts
- graph.ts
- quads.ts
- resolve-graph.ts
- vertex.ts
- <internal>
- DataflowGraphVertexArgument
- DataflowGraphVertexFunctionCall
- DataflowGraphVertexFunctionDefinition
- DataflowGraphVertexInfo
- DataflowGraphVertexUse
- DataflowGraphVertexValue
- DataflowGraphVertexVariableDefinition
- DataflowGraphVertices
- isFunctionCallVertex
- isFunctionDefinitionVertex
- isUseVertex
- isValueVertex
- isVariableDefinitionVertex
- VertexType
- internal
- process
- functions
- call
- argument
- built-in
- built-in-access.ts
- built-in-apply.ts
- built-in-assignment.ts
- built-in-expression-list.ts
- built-in-for-loop.ts
- built-in-function-definition.ts
- built-in-get.ts
- built-in-if-then-else.ts
- built-in-library.ts
- built-in-pipe.ts
- built-in-quote.ts
- built-in-repeat-loop.ts
- built-in-replacement.ts
- built-in-source.ts
- built-in-special-bin-op.ts
- built-in-while-loop.ts
- common.ts
- default-call-handling.ts
- known-call-handling.ts
- named-call-handling.ts
- unnamed-call-handling.ts
- process-argument.ts
- process-parameter.ts
- call
- process-named-call.ts
- process-symbol.ts
- process-uninteresting-leaf.ts
- process-value.ts
- functions
- linker.ts
- process
- cluster.ts
- extractor.ts
- info.ts
- logger.ts
- processor.ts
- documentation
- data
- doc-util
- print-capabilities-markdown.ts
- print-dataflow-graph-wiki.ts
- print-interface-wiki.ts
- print-linting-and-testing-wiki.ts
- print-normalized-ast-wiki.ts
- print-query-wiki.ts
- queries
- catalog
- call-context-query
- cluster-query
- dataflow-query
- dependencies-query
- id-map-query
- lineage-query
- location-map-query
- normalized-ast-query
- static-slice-query
- virtual-query
- base-query-format.ts
- query.ts
- query-print.ts
- two-layer-collector.ts
- catalog
- r-bridge
- data
- lang-4.x
- ast
- model
- nodes
- processing
- collect.ts
- model.ts
- operators.ts
- type.ts
- versions.ts
- parser
- json
- main
- internal
- control
- expression
- functions
- loops
- operators
- other
- structure
- values
- normalize-access.ts
- normalize-meta.ts
- normalizer-data.ts
- internal
- model
- convert-values.ts
- ast
- init.ts
- retriever.ts
- shell.ts
- shell-executor.ts
- reconstruct
- slicing
- criterion
- static
- statistics
- features
- supported
- assignments
- comments
- control-flow
- data-access
- defined-functions
- expression-list
- loops
- used-functions
- used-packages
- values
- variables
- common-syntax-probability.ts
- feature.ts
- post-processing.ts
- supported
- output
- summarizer
- first-phase
- post-process
- second-phase
- auto-detect.ts
- summarizer.ts
- meta-statistics.ts
- statistics.ts
- features
- config.ts
- test
- functionality
which of the arguments should be forced? this may be all, e.g., if the function itself is unknown on encounter