diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-06-24 15:06:22 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-06-24 15:06:22 +0200 |
| commit | 8bfde609e285a8068396490c5399e7913682d19c (patch) | |
| tree | b1b725601d187cbfd761d897e409f01c72c9d978 /compiler/rustc_resolve/src | |
| parent | 94b9ea417dcce52b3600e8840547a6d7ec9a6891 (diff) | |
| parent | 34e6ea1446c3826b69af70ea10b1484eba1de931 (diff) | |
| download | rust-8bfde609e285a8068396490c5399e7913682d19c.tar.gz rust-8bfde609e285a8068396490c5399e7913682d19c.zip | |
Rollup merge of #126414 - ChrisDenton:target-known, r=Nilstrieb
Tier 2 std support must always be known We should never have a tier 2 target without knowing its support status so I think this line in the tier 2 section is a bit wrong: > ? indicates the standard library support is unknown or a work-in-progress. My first inclination was just to drop the "unknown or" part. However, after thinking about it some more, I think we should just use `✓` for this. The only affected targets are UEFI and frankly there are targets with worse std support that are marked with `✓` (e.g. wasm). I think a `✓` should mean "this supports building with std (and is checked in CI for tier 2+)". The target errata can detail the current limitations or special requirements for doing so.
Diffstat (limited to 'compiler/rustc_resolve/src')
0 files changed, 0 insertions, 0 deletions