Remove duplicate section

[Arthur-Milchior]

For some reason the section was duplicated. There was a very minor variation in phrasing; I believe that no information is lost with this PR.

[rustbot]

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @GuillaumeGomez (or someone else) soon.

Please see the contribution instructions for more information. Namely, in order to ensure the minimum review times lag, PR authors and assigned reviewers should ensure that the review label (S-waiting-on-review and S-waiting-on-author) stays updated, invoking these commands when appropriate:

• @rustbot author: the review is finished, PR author should check the comments and take action accordingly
• @rustbot review: the author is ready for a review, this PR will be queued again in the reviewer's queue

[GuillaumeGomez]

r? @Amanieu

[Amanieu]

This isn't exactly duplicated: there is technically a difference between "tier 1" and "tier 1 with host tools", it's just that at the moment these both contain the same set of targets.

Perhaps it would be better to remove this distinction and only refer to these as "tier 1" targets. We could re-introduce the distinction if we ever add a tier 1 target without host tools.

[Arthur-Milchior]

Thank you for the explanation, I think I now have a better understanding of this page.

I could understand it would be easier to keep both sections than to create a new one later. At least to let readers know that they may eventually exists tier 1 without host tools. If the distinction exists in Rust community, my goal was really not to change the way concept are referenced.

May I suggest, as you did with tier 2, titling the section explicitly "Tier 1 target without host tools".
Or maybe refactor a little bit, and have a section
"Tier 1 target", with two subsections, "with" and "without" host tools. And do the same for "Tier 2". This would in particular help understand what is in common and what differs between the "with" and the "without" host tools.

Should I open a bug report? I doubt this PR can be merged as-is, and I suspect this discussion may be better in a bug than a PR. Also, if the change is less trivial, it may be done in a different PR than this one

[Amanieu]

I like the idea of making with/without host tools a sub-section of the tier.

If you update your PR to do this then we can move forward with it.

[Arthur-Milchior]

I hope this change will fit your requirement

[bors]

☔ The latest upstream changes (presumably #120196) made this pull request unmergeable. Please resolve the merge conflicts.

[Amanieu]

Looks good!

r=me once conflicts are resolved.

[Amanieu]

ping @Arthur-Milchior can you resolve conflicts and rebase?

[Dylan-DPC]

@Arthur-Milchior any updates on this? thanks

[oskgo]

@Arthur-Milchior

Ping from triage: I'm closing this due to inactivity, Please reopen when you are ready to continue with this.
Note: if you are going to continue please open the PR BEFORE you push to it, else you won't be able to reopen - this is a quirk of github.
Thanks for your contribution.

@rustbot label: +S-inactive