Skip to content

Increase overall strictness of compiler #685

Closed

Description

@evhub

New guidelines:

  • If it's purely a subjective style issue, then it should only ever show up on --strict.

  • If it's a general code cleanliness issue with no syntax for dismissing the issue, then it should only ever show up as a warning.

  • If it's a general code cleanliness issue that has a syntax for dismissing the issue, then it should be a warning regardless and an error on --strict.

  • If it's a deprecated feature, it should be a warning regardless and an error on --strict.

Activity

  1. added this to the v2.1.2 milestone on Nov 15, 2022
  2. added a commit that references this issue on Nov 15, 2022
    74d0935
  3. added a commit that references this issue on Dec 30, 2022
    84a5a46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions