Class FieldDoubleInit

A detector that highlights cases where a field is initialized both in the init function and at the point of definition.

Why is it bad?

Double initialization of fields can either be a programmer's mistake or simply a waste of gas. It is always preferred to initialize values in the field declaration if they have a compile-time evaluatable default value, or in the init function if they must be initialized dynamically.

Example

contract Test {
    a: Int = 0; // Bad
    init(x: Int) { self.a = x }
}

Use instead:

contract Test {
    a: Int; // Fixed
    init(x: Int) { self.a = x }
}

Hierarchy (view full)

Constructors

constructor

Properties

ctx

Accessors

id kind shareImportedWarnings usesSouffle

Methods

check makeWarning skipUnused

Constructors

constructor

Properties

Readonlyctx

ctx: MistiContext

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

ProtectedmakeWarning

ProtectedskipUnused

  • skipUnused(name): boolean

  • Returns true if the identifier with the given name should not be reported by unused variables detectors.

    Parameters

    • name: string

    Returns boolean

Settings

Member Visibility

On This Page

Why is it bad?Example
Constructors
Properties
Accessors
Methods