Skip to content
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

grouping targets in the target list #2171

Open
fbstj opened this issue Jul 28, 2023 · 1 comment
Open

grouping targets in the target list #2171

fbstj opened this issue Jul 28, 2023 · 1 comment
Labels
A-frontend Area: Web frontend E-easy Effort: Should be easy to implement and would make a good first PR S-needs-design Status: There's a problem here, but no obvious solution; or the solution raises other questions

Comments

@fbstj
Copy link

fbstj commented Jul 28, 2023

I came across #2170 and the screenshot inspired me to ask if it makes sense to group the targets by platform tier

image

@Nemo157
Copy link
Member

Nemo157 commented Jul 28, 2023

AFAIK there's no tier metadata published with the targets, https://github.com/rust-lang/rust/blob/master/src/doc/rustc/src/platform-support.md is the only place I know we could get this info.

It might also be that rustc's tiers don't match the crate's tiers, a lot of the time the only reason crates build for more than a single target is that they don't override the default target list. If we're going to provide grouping it might be best set by the crate itself

[[package.metadata.docs.rs.target-groups]]
label = "Fully tested"
targets = [ ... ]
[[package.metadata.docs.rs.target-groups]]
label = "Build only"
targets = [ ... ]

@syphar syphar added A-frontend Area: Web frontend E-easy Effort: Should be easy to implement and would make a good first PR S-needs-design Status: There's a problem here, but no obvious solution; or the solution raises other questions labels Aug 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-frontend Area: Web frontend E-easy Effort: Should be easy to implement and would make a good first PR S-needs-design Status: There's a problem here, but no obvious solution; or the solution raises other questions
Projects
None yet
Development

No branches or pull requests

3 participants