Brodie Gaslam

This also has implications for the size of the stored unitizer. Perhaps by default we should only store 1 character, or none if there is no output, and the default...

Turns out stdout and stderr capture is a very small portion of the storage space taken up in a unitizer. Probably still want to consider noting whether there is stdout/err...

Urgh, inadvertent close. Related to #105.

Really, right thing to do here is to store any stdout produced by the test itself separately from that of printing the result of the test.

More importantly, we really need to store stderr since some code will issue errors via that without actually throwing conditions (for example, stack imbalance warnings).

Possibly related: ``` > treeprof::treeprof(as.factor(grp)) Profiling auto gc: running with gc() first First run in 1.814 seconds Looping to 5 seconds Parsing Rprof Done Ticks: 756; Iterations: 3; Time Per:...

Note this will almost certainly have to be a documentation issue rather than an actual resolution.

This is mostly documented now. Leaving alive in case we think of some way of getting a better resolution. One half-thought was to duplicate objects ahead of tests, compare after,...

Addressed bulk of issues in #194, but can still improve.

We ended up abandoning the idea of unsetting 'unitizer' options due to the extended use of those options by display functions during review, which would have required us to make...