Skip to content

BSL025 — Empty statement

← All rules

Summary

Empty statement

Identifiers

Field Value
Rule code BSL025
Compatible alias EmptyStatement
Severity WARNING
Enabled by default Yes
Implemented Yes
Tags syntax, convention

Behavior

  • The public identifier BSL025 and alias EmptyStatement are stable.
  • The rule reports the cases documented on this page.
  • Suppressions and project configuration are applied before publication.
  • The rule requires neither an external analyzer nor network access.

Configuration and suppression

BSL### is the primary stable identifier. The compatible alias is accepted in select, ignore, and compatible block suppression comments.

[tool.onec-hbk-bsl]
select = ["BSL025"]
ignore = ["EmptyStatement"]

All three suppression families support both a current line and a range. When an opening comment follows code, it affects only that line. Use any one form:

  • noqa:
Value = "example";  // noqa: BSL025
  • bsl-disable:
Value = "example";  // bsl-disable: BSL025
  • compatible BSLLS form:
Value = "example";  // BSLLS:EmptyStatement-off

When the same opening comment is on a line by itself, it starts a range. Close it with the matching marker from the same family:

// noqa: BSL025
// code without this diagnostic
// noqa-enable: BSL025

// bsl-disable: BSL025
// code without this diagnostic
// bsl-enable: BSL025

// BSLLS:EmptyStatement-off
// code without this diagnostic
// BSLLS:EmptyStatement-on

To disable the rule until the end of the file, omit the closing noqa-enable, bsl-enable, or BSLLS:…-on marker.

Opening and closing markers must belong to the same family.

Description

An empty statement is an operator consisting only of a semicolon (";"). Usually appears when:

  • refactoring, when the developer deleted a part of the code, but forgot to delete the last ";"
  • "copy paste", when the developer pasted the copied code containing the final character ";"
  • inattentive, when the developer twice (or even more) times clicked the symbol ";"

An empty statement does not lead to code errors, but clutters it, reducing perception.