fasterthanlime , vor 14 Tagen Englisch Can someone hardcode in rust-analyzer that Future always comes from std::future::Future and not, like, futures_util::Future or something
Can someone hardcode in rust-analyzer that Future always comes from std::future::Future and not, like, futures_util::Future or something
Future
std::future::Future
futures_util::Future
ilmai , vor 12 Tagen Englisch @fasterthanlime same for std vs. portable_atomic please
@fasterthanlime same for std vs. portable_atomic please
jplatte , vor 14 Tagen Englisch @fasterthanlime Yes, this so much! Fortunately even if this is somehow too hard to do in RA, edition 2024 will get rid of the requirement to import Future explicitly once it's out (if you can upgrade to it).
@fasterthanlime Yes, this so much! Fortunately even if this is somehow too hard to do in RA, edition 2024 will get rid of the requirement to import Future explicitly once it's out (if you can upgrade to it).
fasterthanlime OP , vor 14 Tagen Englisch @jplatte > The Rust 2024 Edition is currently slated for release in Rust 1.82.0 can't wait!
@jplatte
> The Rust 2024 Edition is currently slated for release in Rust 1.82.0
can't wait!
Gottox , vor 14 Tagen Englisch @fasterthanlime looks at C23 envies
@fasterthanlime
looks at C23
envies
artificialmind , vor 14 Tagen Englisch @fasterthanlime if we're going down that route. I never want to complete .ne if a .new is available, thank you very much!
@fasterthanlime if we're going down that route. I never want to complete .ne if a .new is available, thank you very much!
.ne
.new