about summary refs log tree commit diff
path: root/src/test/codegen/src-hash-algorithm/src-hash-algorithm-sha1.rs
diff options
context:
space:
mode:
authorYuki Okushi <huyuumi.dev@gmail.com>2020-10-18 04:11:03 +0900
committerGitHub <noreply@github.com>2020-10-18 04:11:03 +0900
commitd10b98d7a5c57369f102f7f15789014ceba8a6c8 (patch)
tree954170e9ebc5cd620e720bc587bd2c831c5e5a80 /src/test/codegen/src-hash-algorithm/src-hash-algorithm-sha1.rs
parent6af9846fcc8797bf97e9fb387385208c2219f3d0 (diff)
parent3522add318f8fbcd96a032f6779be09ba3d80478 (diff)
downloadrust-d10b98d7a5c57369f102f7f15789014ceba8a6c8.tar.gz
rust-d10b98d7a5c57369f102f7f15789014ceba8a6c8.zip
Rollup merge of #75802 - petrochenkov:nometa, r=nikomatsakis
resolve: Do not put nonexistent crate `meta` into prelude

Before the 2018 edition release there was some vague suggestion about adding a crate named `meta` to the standard distribution.
On this basis the name `meta` was "partially reserved" by putting `meta` into extern prelude (this means importing something named `meta` will result in an ambiguity error, for example).
This only caused confusion so far, and two years later there are no specific plans to add such crate.

If some standard crate (named `meta` or not) is added in the future, then cargo will hopefully already have ability to put it into extern prelude explicitly through `Cargo.toml`.
Otherwise, it could be added to extern prelude by the compiler at edition boundary.

Closes https://github.com/rust-lang/rust/issues/73948
Diffstat (limited to 'src/test/codegen/src-hash-algorithm/src-hash-algorithm-sha1.rs')
0 files changed, 0 insertions, 0 deletions