Class PreferBinaryReceiver

A detector that identifies usage of text receivers that could be replaced with binary ones.

Why is it bad?

To prevent conflicts with binary message bodies, text receivers route based on the hash of the message body contents. This is an expensive operation that requires more than 500 units of gas.

See: https://docs.tact-lang.org/book/gas-best-practices/#prefer-binary-receivers-to-text-receivers

Example

receive("one") {}

Use instead:

message(1) One {}
receive(_: One) {}

Hierarchy (view full)

Constructors

constructor

Properties

category ctx severity

Accessors

id kind shareImportedWarnings usesSouffle

Methods

check getCategory getSeverity makeWarning skipUnused

Constructors

constructor

Properties

category

category: Category = Category.OPTIMIZATION

Readonlyctx

ctx: MistiContext

severity

severity: Severity = Severity.LOW

Accessors

id

  • get id(): string

  • Gets the short identifier of the detector, used in analyzer warnings.

    Returns string

    The unique identifier of the detector.

kind

shareImportedWarnings

  • 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

usesSouffle

  • get usesSouffle(): boolean

  • Checks whether this detector needs the Soufflé binary to be executed.

    Returns boolean

Methods

check

getCategory

getSeverity

ProtectedmakeWarning

ProtectedskipUnused

Settings

Member Visibility

On This Page

Why is it bad?Example
Constructors
Properties
Accessors
Methods