Tom Clune

What about the methods that say provide the MPI communicator inside a test? The user's code (and tests) may still be using integers for the communicator and the framework needs...

My main concern was just making sure that the default behavior remains backward compatible. If the default remains "not F08" then we can let the user update the tests themselves...

Interesting. I'm actually a bit surprised this has not come up before, as `t` is hardly a rare variable name. (Perhaps a bit rare as a public module variable ...)...

A related set of comparisons would include tolerances. I'm not sure that these would be truly useful though.

I was not aware of the tarball issue, but it does not surprise me. And I certainly had not anticipated the complication you mention. I intentionally designed the build system...

Yes - that might be preferable. Currently the strategy is to try find_package(). If not FOUND, then it uses submodules. I could add a 2nd check so that if submodules...

Yes I just discovered this myself. And spent the day working through the issue. I've found the culprit, but am waiting to hear back from the contributor in case he...

Yes - I use a tool to generate the extra tar balls. But I sometimes forget. Lately I've been a bit better. But since I cannot build the latest version...

Sorry about that. Proper tar is now uploaded. I hope to get this automated soon.

The `@test` and other annotations are only for user convenience. (Often a very big convenience.) But you may also just want to wrap your test within a pFunit test: ```f90...