robigalia / meta

Added good-first-project os-agnostic labels

Well, the parser can use any std/crates.io crate, but don't we want the emitter to be as thin as possible? After all, it may be something we want to run on the target with a minimal environment, outputting over serial or some such.

Yes, definitely.

So, my thoughts on the emitter API:

let tap = Tap::from(a_write);
tap.plan( 3, |plan| {
    plan.show( "True is equal to itself", true == true );
    plan.show( "A closure is fine too", || true );
    plan.todo( "Not yet implemented" )
        .show( "You can skip things", false );
    plan.show( "And even do so conditionally", |test|
        if true {
            test.skip("Not enough memory")
        } else {
            test.when(super_expensive_fn)
        }
    );
});

The idea is that we'd impl Test for bool, FnOnce() -> bool, and FnOnce(&mut TestCase), and the signature of plan.show() would be fn show<T: Test>(&mut self, &str, T). plan.todo() would return a TodoTest that would borrow the plan mutably, and would have fn show<T: Test>(self, &str, T).

There'd also be

• tap.todo("message")
• tap.skip("message")
• tap.bail("message")
• plan.skip("message")
• test.todo("message")
• test.pass()
• test.fail()

TAP uses YAML blocks as a detailed description. Is it ok to base the emitter on yaml-rust? What kind of properties needs a crate to run on sel4? Is std allowed?

@niclas std isn't allowed, and the emitter shouldn't do any allocations at all. Writing out the YAML blocks shouldn't need it, I don't think. The parser can use anything.

mentioned in merge request sel4-config!3