diff options
| author | bors <bors@rust-lang.org> | 2024-05-01 02:11:29 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-05-01 02:11:29 +0000 |
| commit | 2e88e9e7d0f7d506a71c9eb1b367ecba3d1b2297 (patch) | |
| tree | 08987548346ef70c7348fc7f0fa41ff44b827a64 /src/librustdoc/passes/calculate_doc_coverage.rs | |
| parent | f5355b93ba43e5fbc44e8df5c113116844c43724 (diff) | |
| parent | f9f3573b62107983c22b27dae40d275930f31d4c (diff) | |
| download | rust-2e88e9e7d0f7d506a71c9eb1b367ecba3d1b2297.tar.gz rust-2e88e9e7d0f7d506a71c9eb1b367ecba3d1b2297.zip | |
Auto merge of #124491 - madsmtm:target_vendor-apple, r=workingjubilee
Use `target_vendor = "apple"` instead of `target_os = "..."` Use `target_vendor = "apple"` instead of `all(target_os = "macos", target_os = "ios", target_os = "tvos", target_os = "watchos", target_os = "visionos")`. The apple targets are quite close to being identical, with iOS, tvOS, watchOS and visionOS being even closer, so using `target_vendor` when possible makes it clearer when something is actually OS-specific, or just Apple-specific. Note that `target_vendor` will [be deprecated in the future](https://github.com/rust-lang/rust/issues/100343), but not before an alternative (like `target_family = "apple"`) is available. While doing this, I found various inconsistencies and small mistakes in the standard library, see the commits for details. Will follow-up with an extra PR for a similar issue that need a bit more discussion. EDIT: https://github.com/rust-lang/rust/pull/124494 Since you've talked about using `target_vendor = "apple"` in the past: r? workingjubilee CC `@simlay,` `@thomcc` `@rustbot` label O-macos O-ios O-tvos O-watchos O-visionos
Diffstat (limited to 'src/librustdoc/passes/calculate_doc_coverage.rs')
0 files changed, 0 insertions, 0 deletions