Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement an unused result lint #11754

Closed
wants to merge 2 commits into from

Commits on Jan 28, 2014

  1. Implement an unused_result lint

    I attempted to implement the lint in two steps. My first attempt was a
    default-warn lint about *all* unused results. While this attempt did indeed find
    many possible bugs, I felt that the false-positive rate was too high to be
    turned on by default for all of Rust.
    
    My second attempt was to make unused-result a default-allow lint, but allow
    certain types to opt-in to the notion of "you must use this". For example, the
    Result type is now flagged with #[must_use]. This lint about "must use" types is
    warn by default (it's different from unused-result).
    
    The unused_must_use lint had a 100% hit rate in the compiler, but there's not
    that many places that return Result right now. I believe that this lint is a
    crucial step towards moving away from conditions for I/O (because all I/O will
    return Result by default). I'm worried that this lint is a little too specific
    to Result itself, but I believe that the false positive rate for the
    unused_result lint is too high to make it useful when turned on by default.
    alexcrichton committed Jan 28, 2014
    Configuration menu
    Copy the full SHA
    9896beb View commit details
    Browse the repository at this point in the history

Commits on Jan 29, 2014

  1. 5 Configuration menu
    Copy the full SHA
    c13a625 View commit details
    Browse the repository at this point in the history