Make settings::Flags::new consume the Builder.

This makes it more clear what the relationship is between the Builder
and the resulting Flags.
This commit is contained in:
Dan Gohman
2018-04-27 21:01:35 -07:00
parent b7f38ac8bc
commit 94a883abae
21 changed files with 63 additions and 60 deletions

View File

@@ -101,7 +101,7 @@ pub struct DummyEnvironment {
impl DummyEnvironment {
/// Allocates the data structures with default flags.
pub fn default() -> Self {
Self::with_flags(settings::Flags::new(&settings::builder()))
Self::with_flags(settings::Flags::new(settings::builder()))
}
/// Allocates the data structures with the given flags.

View File

@@ -32,7 +32,7 @@ fn testsuite() {
})
.collect();
paths.sort_by_key(|dir| dir.path());
let flags = Flags::new(&settings::builder());
let flags = Flags::new(settings::builder());
for path in paths {
let path = path.path();
handle_module(&path, &flags);
@@ -43,7 +43,7 @@ fn testsuite() {
fn return_at_end() {
let mut flag_builder = settings::builder();
flag_builder.enable("return_at_end").unwrap();
let flags = Flags::new(&flag_builder);
let flags = Flags::new(flag_builder);
handle_module(&PathBuf::from("../../wasmtests/return_at_end.wat"), &flags);
}