rust/src/test/compile-fail/nested-ty-params.rs

// xfail-stage0
// error-pattern:Attempt to use a type argument out of scope
fn hd[U](&vec[U] v) -> U {
  fn hd1(&vec[U] w) -> U {
    ret w.(0);
  }
  ret hd1(v);
}
Make resolve check for type-variable name-shadowing Capturing a type argument in the enclosing scope should be an error -- this commit implements that check in resolve, avoiding a potential assertion failure in trans. Closes #648. 2011-07-12 15:42:05 -05:00			`// xfail-stage0`
			`// error-pattern:Attempt to use a type argument out of scope`
Emit a better error message for unbound type parameters in nested functions This code was causing a bounds check failure: fn hd[U](&vec[U] v) -> U { fn hd1(&vec[U] w) -> U { ret w.(0); } ret hd1(v); } because in hd1, U was being treated as if it referred to a type parameter of hd1, rather than referring to the lexically enclosing binding for U that's part of hd. I'm actually not sure whether this is a legit program or not. But I wanted to get rid of the bounds check error, so I assumed that program shouldn't compile and made it a proper error message. 2011-06-21 19:56:56 -05:00			`fn hd[U](&vec[U] v) -> U {`
			`fn hd1(&vec[U] w) -> U {`
			`ret w.(0);`
			`}`
			`ret hd1(v);`
			`}`