How to quiet a warning for a single statement in Rust?

by

To silence warnings you have to add the allow(warning_type) attribute to the affected expression or any of its parents. If you only want to silence the warning on one specific expression, you can add the attribute to that expression/statement: 

fn main() {
    #[allow(unused_variables)]
    let not_used = 27;

    #[allow(path_statements)]
    std::io::stdin;

    println!("hi!");
}

However, the feature of adding attributes to statements/expressions (as opposed to items, like functions) is still a bit broken. In particular, in the above code, the std::io::stdin line still triggers a warning. You can read the ongoing discussion about this feature here.

Often it is not necessary to use an attribute though. Many warnings (like unused_variables and unused_must_use) can be silenced by using let _ = as the left side of your statement. In general, any variable that starts with an underscore won’t trigger unused-warnings.

More Related Contents:

  1. How to get mutable references to two array elements at the same time?
  2. How do I synchronously return a value calculated in an asynchronous Future in stable Rust?
  3. Returning a closure from a function
  4. What is this question mark operator about?
  5. Returning a reference from a HashMap or Vec causes a borrow to last beyond the scope it’s in?
  6. How do I convert a Vec to a Vec without copying the vector?
  7. How do you access enum values in Rust?
  8. Situations where Cell or RefCell is the best choice
  9. Cannot infer an appropriate lifetime for autoref due to conflicting requirements
  10. How do I borrow a reference to what is inside an Option?
  11. What is lifetime elision in very simple terms?
  12. Why does this read input before printing?
  13. How to create a String directly?
  14. How to create an in-memory object that can be used as a Reader, Writer, or Seek in Rust?
  15. What’s the Rust idiom to define a field pointing to a C opaque pointer?
  16. Can’t borrow mutably within two different closures in the same scope
  17. Why does my variable not live long enough?
  18. What is the syntax to match on a reference to an enum?
  19. How can I implement Rust’s Copy trait?
  20. How to use a struct’s member as its own key when inserting the struct into a map without duplicating it?
  21. Why can’t I return an &str value generated from a String?
  22. Why are recursive struct types illegal in Rust?
  23. How to implement a custom ‘fmt::Debug’ trait?
  24. What is the prelude?
  25. How to embed resources in Rust executable?
  26. How do I use a crate from another crate without explicitly defining a new dependency in my project?
  27. Extend lifetime of variable
  28. Cannot use moved BufReader after for loop with bufreader.lines()
  29. Expected closure, found a different closure
  30. How can I iterate on an Option?

Leave a Comment