While responding to #96, I realized that greatest should more explicitly guard against calling RUN_TEST inside a test (which was, itself, run via RUN_TEST) -- it doesn't make any effort to handle that kind of nesting, so it will lead to strange behavior.
While responding to #96, I realized that greatest should more explicitly guard against calling
RUN_TESTinside a test (which was, itself, run viaRUN_TEST) -- it doesn't make any effort to handle that kind of nesting, so it will lead to strange behavior.