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

docs(ref): Note MSRV for features in the docs #14224

Merged
merged 1 commit into from
Jul 10, 2024
Merged

Conversation

epage
Copy link
Contributor

@epage epage commented Jul 9, 2024

I mostly focused on manifests and build scripts as those seemed the highest priority.
I also went back only so far, assuming these would be the highest value items.

I mostly focused on manifests and build scripts as those seemed the
highest priority.
I also went back only so far, assuming these would be the highest value
items.
@rustbot
Copy link
Collaborator

rustbot commented Jul 9, 2024

r? @ehuss

rustbot has assigned @ehuss.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

@rustbot rustbot added A-documenting-cargo-itself Area: Cargo's documentation S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jul 9, 2024
Copy link
Member

@weihanglo weihanglo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To me, it's nicer to scan if the MSRV requirement is at the top of the section.

Otherwise LGTM.

@weihanglo
Copy link
Member

To make it more outstanding, maybe we can have an icon noting MSRV requirement.

BTW, this reminds me anchors for environment variables: https://rust-lang.zulipchat.com/#narrow/stream/246057-t-cargo/topic/Anchors.20for.20each.20environment.20variable.20in.20The.20Cargo.20Book

@epage
Copy link
Contributor Author

epage commented Jul 10, 2024

To me, it's nicer to scan if the MSRV requirement is at the top of the section.

I had considered that at one point. I kept it at the bottom because

  • The happy path would be that people not worry about this (especially 5 years out for these specific ones) and so putting it at the top seems to be optimizing for the non-happy path
  • If this grows to need multiple notes on MSRV, then that could really clog things up, hiding away the details that say what the section they are viewing is even about.

@weihanglo
Copy link
Member

The happy path would be that people not worry about this (especially 5 years out for these specific ones) and so putting it at the top seems to be optimizing for the non-happy path

Not entire agree on this. If there is only one line MSRV description, it doesn't really hurt people on the happy path. However, it's easier to slip from users on non-happy path. They are often library authors and may affect more downstream packages. CMake doc is the baseline of what we'll have if moved to the top.

One alternative is adding some styles, like Python documetation and pyproject.toml (which the former is at the bottom and the latter at the top).

For manifest fields for long term, I would like to see a metadata like what we have for configuration about optionality, default value, etc.


Given it is better than none, I am not going to block this. Thanks for the enhancement!

@bors r+

@bors
Copy link
Collaborator

bors commented Jul 10, 2024

📌 Commit 9262ae4 has been approved by weihanglo

It is now in the queue for this repository.

@bors bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Jul 10, 2024
@bors
Copy link
Collaborator

bors commented Jul 10, 2024

⌛ Testing commit 9262ae4 with merge 1d9058f...

@bors
Copy link
Collaborator

bors commented Jul 10, 2024

☀️ Test successful - checks-actions
Approved by: weihanglo
Pushing 1d9058f to master...

@bors bors merged commit 1d9058f into rust-lang:master Jul 10, 2024
22 checks passed
@epage epage deleted the msrv branch July 10, 2024 14:51
bors added a commit to rust-lang-ci/rust that referenced this pull request Jul 17, 2024
Update cargo

31 commits in 154fdac39ae9629954e19e9986fd2cf2cdd8d964..a2b58c3dad4d554ba01ed6c45c41ff85390560f2
2024-07-07 01:28:23 +0000 to 2024-07-16 00:52:02 +0000
- chore(ci): bump CI tools (rust-lang/cargo#14257)
- test: migrate fetch and list_availables to snapbox (rust-lang/cargo#14214)
- chore: downgrade to jobserver@0.1.28 (rust-lang/cargo#14254)
- perf(source): Don't `du` on every git source load (rust-lang/cargo#14252)
- fix(source): Don't warn about unreferenced duplicate packages (rust-lang/cargo#14239)
- feat(test): Add cargo_test to test-support prelude (rust-lang/cargo#14243)
- Add workflow to publish Cargo automatically (rust-lang/cargo#14202)
- test: migrate implicit_features to snapbox (rust-lang/cargo#14245)
- test: migrate build-std/main to snapbox (rust-lang/cargo#14241)
- test: migrate check_cfg to snapbox (rust-lang/cargo#14235)
- refactor(source): More RecursivePathSource clean up (rust-lang/cargo#14231)
- Add more profiling traces (rust-lang/cargo#14238)
- fix(overrides): Don't warn on duplicate packages from using '..' (rust-lang/cargo#14234)
- fix(test): Redact elapsed time in the minutes time frame (rust-lang/cargo#14233)
- test: Migrate lto tests to snapbox (rust-lang/cargo#14209)
- fix: Ensure dep/feature activates the dependency on 2024 (rust-lang/cargo#14221)
- chore(docs): update index of reference (rust-lang/cargo#14228)
- test: migrate test to snapbox (rust-lang/cargo#14226)
- chore: remove duplicate words (rust-lang/cargo#14229)
- docs(contrib): Document things I look for in RFCs (rust-lang/cargo#14222)
- docs(ref): Note MSRV for features in the docs (rust-lang/cargo#14224)
- test(progress): Resolve flakiness (rust-lang/cargo#14223)
- fix(test): Reduce over-prescription to the caller (rust-lang/cargo#14217)
- refactor: move get_source_id out of registry (rust-lang/cargo#14218)
- fix: rename to `rustdoc::broken_intra_doc_links` (rust-lang/cargo#14215)
- test: migrate member_errors, multitarget and new to snapbox (rust-lang/cargo#14210)
- test: migrate generate_lockfile and glob_targets to snapbox (rust-lang/cargo#14200)
- test: Ensure --list test works with cargo-bloat (rust-lang/cargo#14213)
- dont make new constant InternedString in hot path (rust-lang/cargo#14211)
- Fix compatible_with_older_cargo test. (rust-lang/cargo#14212)
- test: migrate metabuild, metadata and net_config to snapbox (rust-lang/cargo#14162)
@rustbot rustbot added this to the 1.81.0 milestone Jul 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-documenting-cargo-itself Area: Cargo's documentation S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants