Fix comment placement in compiletest

This commit is contained in:
Brian Anderson 2011-07-27 11:17:03 -07:00
parent 7647cf73d1
commit 0923d67096

View File

@ -14,31 +14,33 @@ import std::task;
tag mode { mode_compile_fail; mode_run_fail; mode_run_pass; } tag mode { mode_compile_fail; mode_run_fail; mode_run_pass; }
type config = // The library paths required for running the compiler type config = {
// The library paths required for running compiled programs // The library paths required for running the compiler
// The rustc executable compile_lib_path: str,
// The directory containing the tests to run // The library paths required for running compiled programs
// The directory where programs should be built run_lib_path: str,
// The name of the stage being built (stage1, etc) // The rustc executable
// The test mode, compile-fail, run-fail, run-pass rustc_path: str,
// Run ignored tests // The directory containing the tests to run
// Only run tests that match this filter src_base: str,
// A command line to prefix program execution with, // The directory where programs should be built
// for running under valgrind build_base: str,
// Flags to pass to the compiler // The name of the stage being built (stage1, etc)
// Explain what's going on stage_id: str,
{compile_lib_path: str, // The test mode, compile-fail, run-fail, run-pass
run_lib_path: str, mode: mode,
rustc_path: str, // Run ignored tests
src_base: str, run_ignored: bool,
build_base: str, // Only run tests that match this filter
stage_id: str, filter: option::t[str],
mode: mode, // A command line to prefix program execution with,
run_ignored: bool, // for running under valgrind
filter: option::t[str], runtool: option::t[str],
runtool: option::t[str], // Flags to pass to the compiler
rustcflags: option::t[str], rustcflags: option::t[str],
verbose: bool}; // Explain what's going on
verbose: bool
};
fn main(args: vec[str]) { fn main(args: vec[str]) {
@ -230,7 +232,8 @@ So actually shuttling structural data across tasks isn't possible at this
time, but we can send strings! Sadly, I need the whole config record, in the time, but we can send strings! Sadly, I need the whole config record, in the
test task so, instead of fixing the mechanism in the compiler I'm going to test task so, instead of fixing the mechanism in the compiler I'm going to
break up the config record and pass everything individually to the spawned break up the config record and pass everything individually to the spawned
function. */ function.
*/
fn closure_to_task(cx: cx, configport: port[str], testfn: &fn() ) -> task { fn closure_to_task(cx: cx, configport: port[str], testfn: &fn() ) -> task {
testfn(); testfn();