internal compiler error: no type for node 207

[yggie]

Found another bug in the compiler:

error: internal compiler error: no type for node 207: expr 0 (id=207) in fcx 0x112feeb78
note: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: http://doc.rust-lang.org/complement-bugreport.html
note: run with `RUST_BACKTRACE=1` for a backtrace
thread 'rustc' panicked at 'Box<Any>', /Users/rustbuild/src/rust-buildbot/slave/nightly-dist-rustc-mac/build/src/libsyntax/diagnostic.rs:182

stack backtrace:
   1:        0x11193a4b5 - sys::backtrace::write::h64ca2fb259c4ae97lCt
   2:        0x11195c94f - failure::on_fail::h64ff5ae6887860cc0Hz
   3:        0x1118c85ca - rt::unwind::begin_unwind_inner::h1d4bc098fd350446Qpz
   4:        0x10f5dd0b7 - rt::unwind::begin_unwind::h1123425023578864118
   5:        0x10f5dda28 - diagnostic::Handler::bug::h6d2bfe842975d6e0tWF
   6:        0x10ebe0788 - session::Session::bug::h5da8d79b0a6f5276iRq
   7:        0x10e6b1417 - check::FnCtxt<'a, 'tcx>::node_ty::h3ab6d781f2a5ddcdxcm
   8:        0x10e6c2a56 - check::writeback::WritebackCx<'cx, 'tcx>::visit_node_id::hf436b97f4e161626bEb
   9:        0x10e6c0823 - check::writeback::WritebackCx<'cx, 'tcx>.Visitor<'v>::visit_expr::hee82ea3c874784f7bub
  10:        0x10e6c0a8d - check::writeback::WritebackCx<'cx, 'tcx>.Visitor<'v>::visit_expr::hee82ea3c874784f7bub
  11:        0x10e6c0a8d - check::writeback::WritebackCx<'cx, 'tcx>.Visitor<'v>::visit_expr::hee82ea3c874784f7bub
  12:        0x10e6c1e2f - check::writeback::WritebackCx<'cx, 'tcx>.Visitor<'v>::visit_block::hfa817df1b830707aqvb
  13:        0x10e743de0 - check::check_bare_fn::h92d153344310f88bH3j
  14:        0x10e747730 - check::check_method_body::ha4ecd15503ff3b95Zvk
  15:        0x10e73e1ba - check::check_item::hffd8f154a5736127umk
  16:        0x10e7435e2 - visit::walk_mod::h2814595271141058644
  17:        0x10e7435ed - visit::walk_mod::h2814595271141058644
  18:        0x10e80307a - check_crate::unboxed_closure.30671
  19:        0x10e7fe873 - check_crate::h32fc7f8788be683523x
  20:        0x10e171982 - driver::phase_3_run_analysis_passes::h4c5cf0d8fe5d55degwa
  21:        0x10e158420 - driver::compile_input::h31580cbd7ea87613xba
  22:        0x10e223fda - monitor::unboxed_closure.22557
  23:        0x10e222735 - thunk::F.Invoke<A, R>::invoke::h6367419564961841226
  24:        0x10e221510 - rt::unwind::try::try_fn::h7763956589852599824
  25:        0x1119c32a9 - rust_try_inner
  26:        0x1119c3296 - rust_try
  27:        0x10e221c0c - thunk::F.Invoke<A, R>::invoke::h16724184168577887652
  28:        0x11194a154 - sys::thread::thread_start::hbd8f2f8bdd3a3baadrw
  29:     0x7fff890f22fc - _pthread_body
  30:     0x7fff890f2279 - _pthread_body

This is the output from rustc --version --verbose:

rustc 1.0.0-nightly (44a287e6e 2015-01-08 17:03:40 -0800)
binary: rustc
commit-hash: 44a287e6eb22ec3c2a687fc156813577464017f7
commit-date: 2015-01-08 17:03:40 -0800
host: x86_64-apple-darwin
release: 1.0.0-nightly

[kmcallister]

Do you have an example of code that produces this crash?

[yggie]

I managed to reproduce the error in the Rust play-pen: http://is.gd/TRQC8f. I will copy the snippet here anyway:

use std::mem;

struct Foo;

impl Foo {
  fn something(&self) -> u32 {
    mem::transmute(self.non_existent[0])
  }
}

fn main() {
  let foo = Foo;
  foo.something();
}

[ctennis]

A simpler repro:

struct Foo;

fn main() { Foo.asdf[3] }