ICE when compiling with --pretty=typed option

[edwardw]

$ rustc --pretty=typed src/test/run-pass/let-var-hygiene.rs
...
pub fn main() {
    let _x = (8 as int);
    ({
         let given_val =
             (&((({ let _x = (9 as int); (_x as int) } as int)) as int) as
                 &int);
         let expected_val = (&(((8 as int)) as int) as &int);
         (if (!(((((((*(given_val as &int) as int) ==
                        (*(expected_val as &int) as int) as bool)) as bool) &&
                     ((((*(expected_val as &int) as int) ==
                           (*(given_val as &int) as int) as bool)) as bool) as
                     bool)) as bool) as bool) {
              ({
                   #[inline]
                   fn run_fmt(fmt: &::std::fmt::Arguments) -> ! {
                       ((::std::rt::begin_unwind_fmt as
                            fn(&std::fmt::Arguments<>, &'static str, uint) -> !)((fmt
:error: internal compiler error: node_id_to_type: no type for node `expr 5u (id=74)`
This message reflects a bug in the Rust compiler. 
We would appreciate a bug report: http://static.rust-lang.org/doc/master/complement-bugreport.html

$ rustc -v
rustc 0.10-pre
host: x86_64-apple-darwin

[huonw]

Whoa that's some ugly output! :(

This is caused by the assert_eq expanding to something including format, which in turn expands to something with a fixed length vector, and these make --pretty typed unhappy. Thanks for the report, but this is almost certainly a dupe of #4264.