Thanks for the PR. I assume you crafted this from my suggestion in #48?

We rearranged some APIs on the tentative base reporter interface, which I merged yesterday in #71.

There, instead of open() and close(), we have an API set consisting of initialize/finalize (to acquire/release resources that are needed by a reporter during its object lifetime), read/write (for benchmark record IO), and batched versions thereof.

We decided to (temporarily) not go ahead with open() and close() because they are too specific to the file case.
FWIW, the Beam file-based sink, which was our main inspiration for the API set presented in #48, is directly tied to file IO as well.

That's not to say that this is useless, though. I'm wondering how we could use such an abstraction to abstractify file writes to whichever format we like, such as JSON, YAML, TOML, the usual suspects.

If you'd like to get involved in that, I would suggest the following:

1. Pull in current main, and create a feature branch for a file reporter.
2. Add a Python file in src/nnbench/reporter/, maybe file.py, which holds the file reporter.
3. The constructor should take a result directory, which we save the records to.
4. The initialize() method should create this directory, if not already existent.
5. The read() method should open a single file in that directory, and parse the data with the given format, like e.g. JSON, TOML, YAML.
6. The write() method should write the record to a file in that directory, just like you implemented here.
7. Finalize can be empty, or optionally destroy the directory again if you'd like.

Once we have that, we can think about how to make this work across file formats. How does that sound?

I got your point, I will try creating a generic file reporter.