rust/src/test/run-fail/bug-811.rs

// error-pattern:quux
fn test00_start(ch: chan_t<int>, message: int) { send(ch, copy message); }

type task_id = int;
type port_id = int;

type chan_t<T: send> = {task: task_id, port: port_id};

fn send<T: send>(ch: chan_t<T>, -data: T) { fail; }

fn main() { fail "quux"; }
Use actual type, not declared type, when zeroing move arguments trans was failing with a bounds check error because the caller was using the declared type (an out-of-scope ty param) and not the actual type in a list of argument types to zero. Closes #811 2011-08-10 17:57:03 -05:00			`// error-pattern:quux`
Update some more tests for 1a68a9882 2011-11-03 05:14:48 -05:00			`fn test00_start(ch: chan_t<int>, message: int) { send(ch, copy message); }`
Use actual type, not declared type, when zeroing move arguments trans was failing with a bounds check error because the caller was using the declared type (an out-of-scope ty param) and not the actual type in a list of argument types to zero. Closes #811 2011-08-10 17:57:03 -05:00
			`type task_id = int;`
			`type port_id = int;`

Switch to new param kind bound syntax And remove support for the old syntax 2012-01-05 08:35:37 -06:00			`type chan_t<T: send> = {task: task_id, port: port_id};`
Use actual type, not declared type, when zeroing move arguments trans was failing with a bounds check error because the caller was using the declared type (an out-of-scope ty param) and not the actual type in a list of argument types to zero. Closes #811 2011-08-10 17:57:03 -05:00
Switch to new param kind bound syntax And remove support for the old syntax 2012-01-05 08:35:37 -06:00			`fn send<T: send>(ch: chan_t<T>, -data: T) { fail; }`
Use actual type, not declared type, when zeroing move arguments trans was failing with a bounds check error because the caller was using the declared type (an out-of-scope ty param) and not the actual type in a list of argument types to zero. Closes #811 2011-08-10 17:57:03 -05:00
			`fn main() { fail "quux"; }`