Gets the short identifier of the detector, used in analyzer warnings.
The unique identifier of the detector.
Gets the kind of the detector.
Defines the behavior of warnings generated by this detector when working with multiple projects within a single Tact configuration.
Here are the available options:
"union"
Leave this value if you don't care about warnings generated in other projects."intersect"
If the warning is generated for some source location of the imported file,
it should be generated by each of the projects. Example: Constants from an
imported file should not be reported iff they are unused in all the projects,
so you need "intersect".Checks whether this detector needs the Soufflé binary to be executed.
Executes the detector's logic to check for issues within the provided compilation unit.
The compilation unit to be analyzed.
List of warnings has highlighted by this detector.
Protected
makeA wrapper method that creates Misti warnings with additional context about the detector generated it.
Protected
skip
A detector that identifies improper use of exit codes outside the developer-allowed range.
Why is it bad?
In the TON blockchain, exit codes are divided into specific ranges: 0 to 127 are reserved for the TVM or FunC, and 128 to 255 are reserved for Tact. This structure leaves the range from 256 to 65535 for developers to define custom exit codes.
When exit codes are defined outside this allowed range, it may lead to conflicts with existing reserved codes, causing unintended behavior or errors in the contract.
Example
Use instead:
Resources