Skip to content

Rename lint to something else #3517

Closed
Closed
@brson

Description

@brson
Contributor

It has outgrown its original purpose and is becoming the general error reporting mechanism.

Activity

graydon

graydon commented on Mar 25, 2013

@graydon
Contributor

non-critical for 0.6, de-milestoning

alexcrichton

alexcrichton commented on May 14, 2013

@alexcrichton
Member

Is this still a relevant issue? It doesn't seem to me like it's a general error reporting mechanism any more. I think of span_err/span_note/span_warn more along those lines. The lint module in my opinion does indeed have true "lint" passes for code like unused variables, mutability, imports, and assignments.

I'd personally be in favor of keeping it named lint, but I could also do the renaming if there's a better name!

emberian

emberian commented on Jul 12, 2013

@emberian
Member

It isn't error reporting, it's specifically warnings, that aren't about invalid code. Closing, as it no longer seems relevant.

added 2 commits that reference this issue on Apr 27, 2024

Auto merge of rust-lang#3517 - RalfJung:env-vars, r=RalfJung

Auto merge of rust-lang#3517 - RalfJung:env-vars, r=RalfJung

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-lintsArea: Lints (warnings about flaws in source code) such as unused_mut.C-cleanupCategory: PRs that clean code up or issues documenting cleanup.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @graydon@alexcrichton@brson@emberian

        Issue actions

          Rename lint to something else · Issue #3517 · rust-lang/rust