Closed BohuTANG closed 3 years ago
Thanks for the report. I couldn't reproduce this with the snippet you provide, so I have a few questions:
![feature(generators, proc_macro_hygiene, stmt_expr_attributes)]
Are these attributes set at the crate level (lib.rs
or main.rs
)? #![feature(..)]
do not work at the module level. As unused_attributes
warn this, futures-async-stream docs don't explain about this carefully.
- cargo +nightly clippy
Does this issue also happen with Cargo's subcommand, like cargo build
?
It's on module level, if I set it on the lib.rs, it's another problem. Any way to do it in the module level? If not, does rust attribute not allow it?
There is no way to enable unstable features at the module level. What problems do you have when using it at the crate level?
Oh, my mistake. It works now.
futures-async-stream is great, but I had some problems trying it out. I'm not sure if it's related to futures-async-stream(If it's not, then sorry).
rustc version:
code snippe Cargo.toml