Rust wants

[repi]

Wish list of rust compiler & std features & bug fixes we would like to see added/improved/fixed based on the Rust projects we've been developing at Embark.

This is not a complete list, but an attempt to keep a bit of structure for our own sake, and may be of interest for rust compiler developers as well.

Should have

rust compiler features or fixes that would directly improve or help our workflows

• Be able to specify which targets are valid in a workspace #41
• f64::from(bool) and f32::from(bool) rust-lang/rust#74015
• Cause a debug break when a panic occurs on Windows. rust-lang/rust#34502
• Add ability to ignore tests at runtime. rust-lang/rust#68007
• Tracking issue for RFC 2963: rustdoc JSON backend rust-lang/rust#76578
• Support for showing explicit enum discriminant values in rustdoc rust-lang/rust#101337
• match-then-remake Result doesn't optimize away for some payload widths rust-lang/rust#101210
• Use lld by default on x64 msvc windows rust-lang/rust#71520
• cargo install should run cargo audit rust-lang/cargo#10016
• Compilation inconsistency when referencing the same code over path and git/version rust-lang/cargo#7850
• "cargo install" apparently ignores "Cargo.lock" as opposed to "cargo build" rust-lang/cargo#7169
• Tracking Issue for RFC 3028: Allow "artifact dependencies" on bin, cdylib, and staticlib crates rust-lang/cargo#9096
• Tracking Issue for multidep rust-lang/cargo#10030
• Tracking Issue for per-package-target rust-lang/cargo#9406
• Inform build scripts whether cargo is checking or building rust-lang/cargo#4001
• Rustup (including proxies) is not safe for concurrent use rust-lang/rustup#988
• RFC: Nested Cargo packages rust-lang/rfcs#3452
• Tracking issue for RFC 2412, "The optimize attribute" rust-lang/rust#54882
• Tracking Issue for Parallel Rustc Front-end rust-lang/rust#113349
• Target configuration for binaries rust-lang/cargo#9208
• User control over cargo warnings rust-lang/cargo#12235
• lldb can not print Option<i32> rust-lang/rust#79530

Nice to have

rust compiler features or fixes that would be nice to have, but are lower priority to us than the above list.

• docs not loading properly in Safari unless Develop Menu is enabled rust-lang/rust#85444
• cargo fix renames unused local variables from foo to _foo rust-lang/rust#54196
• Nested workspaces rust-lang/cargo#5042
• Tracking Issue for JSON timings rust-lang/cargo#10857
• Feature Request static asserts rust-lang/rfcs#2790
• Consider making the src cache read-only. rust-lang/cargo#9455
• IPv6-Only Hosts Fail to Build rust-lang/cargo#10711
• Hermetic build mode rust-lang/cargo#9506
• Warning when large binary files are included into the bundle rust-lang/cargo#9058
• Cargo timings graph is broken in Firefox rust-lang/cargo#8850
• Tracking Issue for must_not_suspend lint (RFC #3014) rust-lang/rust#83310
• Windows builds are not deterministic with --crate-type=bin and path-prefix remapping rust-lang/rust#88982
• Unsafe fields rust-lang/rfcs#3458

Not filed / found

Fixes or enhancements that believe there is no issue for yet, if you find one please do comment and we'll update it here.

---

Related tracking issues for other Rust components:

• Clippy wants #79
• rustfmt wants #83
• rust-analyzer wants #86

[yanganto]

Hi @repi

Ignore issue is listed in your Should have section.

There is a crate test_with that helps you ignore test cases with conditions. Is it solve your problem? This crate tries to handle this, once Rust can ignore it in runtime, the crate will handle that, so you will not worry about that in the future.

If your use cases are different, could you tell me more about this? Thanks, and happy new year.

[repi]

@yanganto thanks for the reference, and no I don't think it solves it, we need to determine if a test should be run at runtime

[yanganto]

Hi @repi
Now test_with has a test runner and can check the condition on runtime.
https://github.com/yanganto/test-with#runtime
This may be a solution for you.
If you have some condition not provided now, it is welcome to let me know.