-
Notifications
You must be signed in to change notification settings - Fork 13k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add readable rustdoc display for RISC-V target #91518
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @ollie27 (or someone else) soon. Please see the contribution instructions for more information. |
909383b
to
4d457de
Compare
use format 'RISC-V RV32' and 'RISC-V RV64'
4d457de
to
39d99a1
Compare
Edit: after discussions with TUNA members the format used here are 'RISC-V RV32' and 'RISC-V RV64'. Now this pull request may be ready for review. r? @ollie27 |
The idea of this change seems good to me, but I think the names should be |
Any update on this @luojia65 ? |
@GuillaumeGomez It's okay for me, no further updates :) |
Well, we can always update the text later on. Thanks! @bors: r+ rollup |
📌 Commit 39d99a1 has been approved by |
Rollup of 4 pull requests Successful merges: - rust-lang#91518 (Add readable rustdoc display for RISC-V target) - rust-lang#95281 (Fix inaccurate function name in `rustc_const_eval` docs) - rust-lang#96898 (logging: add env var to control verbose scope entry/exit logging) - rust-lang#96936 (:arrow_up: rust-analyzer) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
This pull request adds a human readable rustdoc display for RISC-V architecture. Target configuration marked as
#[cfg(target_arch = "riscv32")]
or#[cfg(target_arch = "riscv64")]
are pretty formatted likeRISC-V RV32
andRISC-V RV64
in Rust docs.Before:
After: