Jim Porter

@JohnGalbraith I just noticed that I failed to "@" you in the previous comment. :/ Doing so here in case you missed it.

> One still has to figure out what the `_` means in either case. This was the main dissonance I had to deal with when trying out Mettle the first...

Do you just mean an index or (global) table or contents, or do you mean something more like a reference page that describes all the functions/classes exposed in the API?

I'm open to suggestions on how the API should look. So far, I have three possibilities: 1. Add a new `.xfail_test` member function that works like `.test` except that it...

> This has my vote! For now, I just hack in #if 0 / #endif around works in progress. You can also use the `skip` attribute in this case. It'll...

@darenw What are your opinions on what should happen if an xfailed test actually _passes_? Should that be treated as ok, or should it report an error?

Hmm. On the one hand, the benefit of reporting an error if an xfailed test passes is that it alerts you to the fact that you fixed the test. However,...

`--pipe-stdout`/`--pipe-stderr` probably makes the most sense then (though I guess it's not really a pipe, so I'll have to make a better name).

This is fixed in GCC 11 and backported to GCC 9 and 10, so once we drop support for earlier versions, the workaround can be removed.

How do you want the seed to work for each test within the suite? For a particular run, should a) each test start with the same seed, b) each test...