Closed
Description
$ cat /tmp/test.rs
use::{{}e::{{}}};
$ RUST_BACKTRACE=1 rustc /tmp/test.rs
error: expected `,`, found `e`
--> /tmp/test.rs:1:9
|
1 | use::{{}e::{{}}};
| ^
error: internal compiler error: unexpected panic
note: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports
note: rustc 1.25.0-nightly (ae920dcc9 2018-01-22) running on x86_64-unknown-linux-gnu
note: run with `RUST_BACKTRACE=1` for a backtrace
thread 'rustc' panicked at 'path resolved multiple times (PathResolution { base_def: Mod(DefId(0/0:0)), unresolved_segments: 0 } before, PathResolution { base_def: Err, unresolved_segments: 0 } now)', librustc_resolve/lib.rs:3733:13
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
stack backtrace:
0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
1: std::sys_common::backtrace::print
at libstd/sys_common/backtrace.rs:68
at libstd/sys_common/backtrace.rs:57
2: std::panicking::default_hook::{{closure}}
at libstd/panicking.rs:380
3: std::panicking::default_hook
at libstd/panicking.rs:390
4: std::panicking::rust_panic_with_hook
at libstd/panicking.rs:576
5: std::panicking::begin_panic
at libstd/panicking.rs:537
6: std::panicking::begin_panic_fmt
at libstd/panicking.rs:521
7: rustc_resolve::Resolver::smart_resolve_path_fragment
8: rustc_resolve::Resolver::smart_resolve_path
9: rustc_resolve::Resolver::resolve_use_tree
10: rustc_resolve::Resolver::resolve_use_tree
11: rustc_resolve::Resolver::resolve_use_tree
12: rustc_resolve::Resolver::resolve_item
13: rustc_resolve::Resolver::resolve_crate
14: rustc::util::common::time
15: rustc_driver::driver::phase_2_configure_and_expand
16: rustc_driver::driver::compile_input
17: rustc_driver::run_compiler