# Stratego API¶

The Statix solver can be called from a Stratego Transformation using the API in the Statix Runtime project. After analysis is executed, the analysis result can be queried using other strategies. In this section, we provide an overview of the availble strategies.

The public API of the Statix runtime is available here. This API strongly depends on the Spoofax constraint analysis library, which is available in the Spoofax Meta Library.

## Single-File Analysis¶

stx-editor-analyze(pre, post|spec-name, init-constraint)


Type: AnalysisAction -> AnalysisResult.

Applies single-file analysis with the specification provided in the arguments. Since this strategy only performs single-file analysis, the current term should always have AnalyzeSingle as top-level constructor. The term and strategy arguments are explained in the following table:

Argument Type Default Description
pre AST -> AST id Transformation to apply before analyzing. This transformation receives the 'parsed AST'.
post AST -> AST id Transformation to apply before analyzing. This transformation receives the result of applying pre to the 'parsed AST', and yields the 'analyzed AST'.
spec-name String The full path to the root module of the specification.
file-constraint String The name of the constraint that should be applied to the pre-transformed AST of each file in the project. This may be a fully qualified name in the form $Module!$ConstraintName, or just a $ConstraintName. In the latter case, the name will be qualified with the spec-name argument. This constraint should have the (Statix) type : scope * Start ## Concurrent Analysis¶ stx-editor-analyze(pre, group, post|spec-name, project-constraint, group-constraint, file-constraint)  Type: AnalysisAction -> AnalysisResult. Applies concurrent multi-file analysis with the specification provided in the arguments. Since this strategy only performs multi-file analysis, the current term should always have AnalyzeMulti as top-level constructor. This strategy chooses the solver based on the metaborg.yaml configuration of the project and the language, but fails with a fatal error if the concurrent solver is not enabled on this project. The term and strategy arguments are explained in the following table: Argument Type Description pre AST -> AST Transformation to apply before analyzing. This transformation receives the 'parsed AST'. group (Resource * AST) -> List(String) Strategy that decides in which group a resource is analyzed. Should return a list with the identifiers of the groups in which the resource should be analyzed. post AST -> AST Transformation to apply before analyzing. This transformation receives the result of applying pre to the 'parsed AST', and yields the 'analyzed AST'. spec-name String The full path to the root module of the specification. project-constraint String The name of the constraint that should be applied to the global scope once. This may be a fully qualified name in the form $Module!$ConstraintName, or just a $ConstraintName. In the latter case, the name will be qualified with the spec-name argument. This constraint should have the (Statix) type : scope
group-constraint String The name of the constraint that should be applied to the each group. This may be a fully qualified name in the form $Module!$ConstraintName, or just a $ConstraintName. In the latter case, the name will be qualified with the spec-name argument. This constraint should have the (Statix) type : scope * string * scope file-constraint String The name of the constraint that should be applied to the pre-transformed AST of each file in the project. This may be a fully qualified name in the form $Module!$ConstraintName, or just a $ConstraintName. In the latter case, the name will be qualified with the spec-name argument. This constraint should have the (Statix) type : scope * Start

## Constraint Evaluation¶

stx-evaluate(|spec-name, constraint)


Type: List(Term) -> Term

Evaluates a functional constraint. The terms in the current term are passed as argument to the constraint, and the result term is the output term of the constraint.

Argument Type Description
spec-name String The full path to the root module of the specification.
constraint String The name of the constraint that should be applied to the term arguments.

## Analysis Errors¶

stx-analysis-has-errors = stx--analysis-has-errors


Type: Analysis -> Analysis

Fails if the current term has no errors, succeeds otherwise.

Last update: 2021-11-15