Thanks to visit codestin.com
Credit goes to github.com

Skip to content
Merged
Changes from 1 commit
Commits
Show all changes
20 commits
Select commit Hold shift + click to select a range
7e64f29
Update Readme
atouchet Jan 15, 2024
aa72e54
Un-hide `iter::repeat_n`
scottmcm Jan 17, 2024
06a9dbe
Fix a soundness bug in `with_tables`.
oli-obk Jan 19, 2024
61361c1
Fix `Stable` trait and its impls to work with the new `with_tables`
oli-obk Jan 19, 2024
9aace67
Ensure internal function is safe
celinval Jan 18, 2024
6cd6539
Use the new `with_tables` everywhere
oli-obk Jan 19, 2024
5796b3c
fix: Drop guard was deallocating with the incorrect size
the8472 Jan 19, 2024
270f151
rustc_mir_dataflow: Add exports for external tools
jubnzv Jan 20, 2024
f6b3bcc
Capture the rationale for -Zallow-features= in bootstrap.py
dtolnay Jan 20, 2024
7842043
Add a warning comment
jubnzv Jan 20, 2024
cc8e56b
Warn users about limited review for tier 2 and 3 code
Mark-Simulacrum Jan 20, 2024
6f1944d
Document some alternatives to `Vec::split_off`
Zalathar Jan 21, 2024
7119ca1
Rollup merge of #120005 - atouchet:rd3, r=Mark-Simulacrum
matthiaskrgr Jan 21, 2024
092d627
Rollup merge of #120045 - scottmcm:unhide-repeat-n, r=Mark-Simulacrum
matthiaskrgr Jan 21, 2024
a72d6c1
Rollup merge of #120128 - oli-obk:smir_internal_lift, r=celinval
matthiaskrgr Jan 21, 2024
4a941d3
Rollup merge of #120145 - the8472:fix-inplace-dest-drop, r=cuviper
matthiaskrgr Jan 21, 2024
e59a6fe
Rollup merge of #120158 - jubnzv:120130-mirdf-exports, r=nnethercote
matthiaskrgr Jan 21, 2024
ac71369
Rollup merge of #120167 - dtolnay:bootstrap, r=clubby789
matthiaskrgr Jan 21, 2024
1229d4c
Rollup merge of #120174 - Mark-Simulacrum:link-libs-policy, r=dtolnay
matthiaskrgr Jan 21, 2024
3eb7fe3
Rollup merge of #120180 - Zalathar:vec-split-off-alternatives, r=dtolnay
matthiaskrgr Jan 21, 2024
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Warn users about limited review for tier 2 and 3 code
  • Loading branch information
Mark-Simulacrum committed Jan 20, 2024
commit cc8e56b1e93ada97a32fa7b5c6482e1f20963ca6
18 changes: 18 additions & 0 deletions src/doc/rustc/src/platform-support.md
Original file line number Diff line number Diff line change
Expand Up @@ -72,6 +72,12 @@ ensure that each tier 2 target can be used as build target after each change. Au
not always run so it's not guaranteed to produce a working build, but tier 2
targets often work to quite a good degree and patches are always welcome!

Tier 2 target-specific code is not closely scrutinized by Rust team(s) when
modifications are made. Bugs are possible in all code, but the level of quality
control for these targets is likely to be lower. See [library team
policy](https://std-dev-guide.rust-lang.org/policy/target-code.html) for
details on the review practices for standard library code.

Tier 2 targets with host tools additionally support running tools like `rustc`
and `cargo` natively on the target, and automated builds ensure that the host
tools build as well. This allows the target to be used as a development
Expand Down Expand Up @@ -121,6 +127,12 @@ The `std` column in the table below has the following meanings:

[`no_std`]: https://rust-embedded.github.io/book/intro/no-std.html

Tier 2 target-specific code is not closely scrutinized by Rust team(s) when
modifications are made. Bugs are possible in all code, but the level of quality
control for these targets is likely to be lower. See [library team
policy](https://std-dev-guide.rust-lang.org/policy/target-code.html) for
details on the review practices for standard library code.

**NOTE:** The `rust-docs` component is not usually built for tier 2 targets,
so Rustup may install the documentation for a similar tier 1 target instead.

Expand Down Expand Up @@ -211,6 +223,12 @@ The `std` column in the table below has the following meanings:

[`no_std`]: https://rust-embedded.github.io/book/intro/no-std.html

Tier 3 target-specific code is not closely scrutinized by Rust team(s) when
modifications are made. Bugs are possible in all code, but the level of quality
control for these targets is likely to be lower. See [library team
policy](https://std-dev-guide.rust-lang.org/policy/target-code.html) for
details on the review practices for standard library code.

The `host` column indicates whether the codebase includes support for building
host tools.

Expand Down