Design meeting: Rust issues encountered by new Rust users in the Bevy project about lang-team

[alice-i-cecile]

I've gathered feedback from the community in this Discord thread, if you're interested in a sneak peek.

[Jules-Bertholet]

Highlights of Discord thread:

• no variadic generics (ugly macros, terrible error messages, cluttered docs…)
• having to install MSVC on Windows (though maybe things are better now that rustup handles it?)
• orphan rules, deriving traits on 3rd-party types
• object safety, needing to go back and redesign traits
• learning macros
• derive + PhantomData footgun (lack of perfect derive)
• cargo features aren't clearly listed in rustdoc
• lifetimes (where/when do they need to be annotated)
• async
• functional update syntax (...default() })
• missing const floats, const traits
• examples in rustdoc
• showing the value of Default::default() in rustdoc
• dynamic linking (inscrutable error messages)
• closure capture rules
• field init shorthand
• target folder not cleaned up after compiler updates
• rust-analyzer and cargo competing for locks on the target folder, grows without bound
• src links don't appear for bevy on docs.rs (due to dynamic linking stuff?)
• browsing all implementors of a trait (rustdoc list is cluttered, hard to skim)
• people don't know about cargo doc --open
• hard to get list of all methods available on a type (including from important traits)
• reborrowing (and lack of it with custom smart pointers)
• newtype/delegation is cumbersome, .0 spam

[Lokathor]

Made a Zulip thread: https://rust-lang.zulipchat.com/#narrow/stream/213817-t-lang/topic/Design.20meeting.3A.20Rust.20issues.20with.20new.20Bevy.20users