An optional detector that highlights messages with implicitly defined opcode.

Tact automatically generates these unique IDs (opcodes) for every received message, but developers can specify a message opcode explicitly. This enables handling of specific opcodes in the receiver explicitly, which may be convenient when interacting with FunC contracts.

See:

message TokenNotification {
  forwardPayload: Slice as remaining;
}

Use instead:

message(0x7362d09c) TokenNotification {
  forwardPayload: Slice as remaining;
}

Hierarchy (view full)

Constructors

Properties

category: Category = Category.BEST_PRACTICES
severity: Severity = Severity.INFO

Accessors

  • get id(): string
  • Gets the short identifier of the detector, used in analyzer warnings.

    Returns string

    The unique identifier of the detector.

  • get shareImportedWarnings(): WarningsBehavior
  • Defines the behavior of warnings generated by this detector when working with multiple projects within a single Tact configuration.

    Here are the available options:

    1. "union" Leave this value if you don't care about warnings generated in other projects.
    2. "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".

    Returns WarningsBehavior

  • get usesSouffle(): boolean
  • Checks whether this detector needs the Soufflé binary to be executed.

    Returns boolean

Methods