Brodie Gaslam
Brodie Gaslam
How do we handle reference objects that are modified by subsequent tests: ``` DT
Technically we can retrieve the stuff out of the `unitizer`s that are returned, but this isn't well documented, etc.
Right now accepting multiple tests leads to three prompts: ``` unitizer> YY 1. res . . . . . . . . . . . . . . . ....
In this cases, we have no changes, only unreviewed, should consider not prompting, particularly if it is a fast evaluation: ``` - New -------------------------------------------------------------------------- | The following test is new....
It is a bit disorienting when a test is accepted/rejected and the next test comes along with a lot of screen output. We need some visual cue to let us...
Right now we use ENTER at an empty prompt to re-prompt, which is a pretty wasteful use of the simplest key stroke. Particularly in `review` mode, it would be nice...
Currently we're resetting state without checking whether the state should be from a reference or a new object. This is an issue with deleted items for which clearly the state...
For example, not sure it should come up in this instance where we just put an arbitrary expression at the prompt: ``` > validate(INT.1 || NULL || LGL, "hello", format...
In particular, stuff like: ``` Warning: stack imbalance in '.Call', 178 then 177 Warning: stack imbalance in 'withVisible', 170 then 169 Warning: stack imbalance in '