diff options
| author | bors <bors@rust-lang.org> | 2018-09-10 10:28:53 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2018-09-10 10:28:53 +0000 |
| commit | 595345419d12c3ea860151df52f78744a31bafff (patch) | |
| tree | 60b6af371b197266ec08e1a37e9a3a0ec65d1114 /src/test/incremental/thinlto | |
| parent | b8d45da2747c0b0943f48854e653ebe0d1ba60c9 (diff) | |
| parent | d5da94a3b1e635eeb9520b87f6414ff3c24c8602 (diff) | |
| download | rust-595345419d12c3ea860151df52f78744a31bafff.tar.gz rust-595345419d12c3ea860151df52f78744a31bafff.zip | |
Auto merge of #54011 - eddyb:anchored-in-the-future, r=petrochenkov
rustc_resolve: inject `uniform_paths` canaries regardless of the feature-gate, on Rust 2018. This PR is an attempt at future-proofing "anchored paths" by emitting the same ambiguity errors that `#![feature(uniform_paths)]` would, with slightly changed phrasing (see added UI tests). Also, on top of #54005, this PR allows this as well: ```rust use crate_name; use crate_name::foo; ``` In that any ambiguity between an extern crate and an import *of that same crate* is ignored. r? @petrochenkov cc @aturon @Centril @joshtriplett
Diffstat (limited to 'src/test/incremental/thinlto')
0 files changed, 0 insertions, 0 deletions
