The fast path allows `RunContext` to skip disabling output redirect, and notifying the reporters, turning `RunContext::notifyAssertionStarted` into a no-op. This improves the overall performance of assertion handling significantly, and also prepares ground for future changes around assertion handling and thread safety. For simple 10M assertion run, this improves the running time by ~30% in Debug build and ~40% in Release build. For backwards-compatibility reasons, the fast path is disabled by default. However, none of the first party reporters use the `assertionStarting` event, so all first party reporters are opted-in.
Catch2 has long since required a standard newer than C++98 so we can safely ignore any warnings related to such old standards.
The license file was renamed with 6a502cc2f5fedd59b3495b58708f0d6d987ed9e1
This also required splitting out Listener factory from the reporter factory hierarchy. In return, the listener factories only need to take in `IConfig const*`, which opens up further refactorings down the road in the colour selection and implementation.
This event listener performs basic consistency checks (akin to matching braces) on events that are passed to the listeners when the `SelfTest` test binary is run. The current checks are about nesting events (e.g. `testCaseStarting` cannot be received before `testRunStarting`, `sectionStarting` can only be received when a test case is active, etc), and matching up counts of starting/ended events. The simplicity means that it could be confused by starting/ended events matching up but being out of order, e.g. ``` * test case A starting * test case B ended * test case B starting * test case A ended ``` would be accepted, even though it is wrong. However, doing full order checking would be much more implementation work, for relatively little benefit, so it is left out for now.
The base was also renamed from `TestEventListenerBase` to `EventListenerBase`, and modified to derive directly from the reporter interface, rather than deriving from `StreamingReporterBase`.
Each of the two reporter bases now has its own header file, and cpp file. Even though this adds another TU to the compilation, the total CPU time taken by compilation is reduced by about 1% for debug build and ~0.5% for optimized build of the main library. (The improvement would be roughly doubles without splitting the TUs, but the maintainability hit is not worth it.) The code size of the static library build has also somewhat decreased. Follow up: Introduce combined TU for reporters, and further split apart the catch_reporter_streaming_base.hpp header into its constituent parts, as it still contains a whole bunch of other stuff.