Closed
Description
Hi,
I'm running into an issue wherein I get unused_parens warnings. A reproducible version on the rust playground can be found here.
The code is
use tokio;
use async_trait::async_trait;
#[async_trait]
trait Resetable {
async fn reset(&mut self);
}
struct Modifier {
action: fn(String) -> String,
}
impl Modifier {
fn new(action: fn(String) -> String) -> Self {
Modifier {
action
}
}
}
#[async_trait]
impl Resetable for Modifier {
async fn reset(&mut self) {
//println!("resetting action");
self.action = |str| str;
}
}
#[tokio::main]
async fn main() {
let mut modifier = Modifier::new(|str| {
format!("{}{}", str, str)
});
let orig = "Frank".to_owned();
let modified = (modifier.action)(orig);
println!("{}", modified);
let _ = modifier.reset().await;
let orig = "Bob".to_owned();
let modified = (modifier.action)(orig);
println!("{}", modified);
}
If i uncomment the println! on line 24 (on the playground), the warning goes away. Do let me know if you would need any more details with this (or, would like me to try something else). Thanks
Activity
dtolnay commentedon Aug 12, 2020
This looks like a strange compiler bug, related to rust-lang/rust#43081. Inserting a
println!("{:#?}", input)
at the beginning of the implementation of async_trait, the tokens being passed as input to the async_trait macro by rustc are:Full token stream
Notice in particular this part:
Rustc inserted unnecessary parentheses around the closure before even calling async_trait, passing the statement as
self.action = (|str| str);
. At the same time, it lost all the location information on the source tokens (#0 bytes(0..0)
) so it blames the user for handwriting those parentheses.dtolnay commentedon Aug 12, 2020
I released 0.1.37 which just suppresses the lint as a workaround.
Aaron1011 commentedon Oct 14, 2020
Now that rust-lang/rust#75734 has been fixed, the lint should no longer fire.