@@ -106,7 +106,6 @@ void compare_files(std::filesystem::path const &baseline,
106106 std::filesystem::path const &challenger,
107107 std::filesystem::path const &json_output,
108108 int const json_indent) {
109-
110109 static constexpr std::string_view p_eq{" probably_equivalent" };
111110 static constexpr std::string_view p_chall_better{
112111 " probably_challenger_better" };
@@ -119,7 +118,7 @@ void compare_files(std::filesystem::path const &baseline,
119118 results_json = {
120119 {" comparing" ,
121120 {
122- {" mode" , " TODO" },
121+ {" mode" , " TODO" }, // will be filled below ...
123122 {" inputs" , nlohmann::json::array ()},
124123 }},
125124 {" total" , {}},
@@ -214,7 +213,9 @@ void compare_files(std::filesystem::path const &baseline,
214213 auto const stats_challenger{
215214 cxxet_pp::stats::compute_from (vals[challenger_ind])};
216215
217- bool const challenger_better{stats_challenger.mean < stats_baseline.mean };
216+ bool const challenger_better{
217+ stats_challenger.mean <
218+ stats_baseline.mean }; // isn't this oversimplification?!
218219
219220 if (challenger_better) {
220221 ++cnt_challenger_better;
@@ -235,9 +236,10 @@ void compare_files(std::filesystem::path const &baseline,
235236 " ) for measurement " + measurement_key_str);
236237
237238 if (!json_output.empty ()) {
238- // even though it's used only one time ... `clangd` got confused by the
239- // nested brackets, etc. and got broken around those strings being
240- // provided directly, at the usage site:
239+ // even though they are used only one time, they are inconveniently
240+ // defined as `std::string_view`s ... because "current" `clangd` got
241+ // confused by the nested brackets, etc. and got broken around those
242+ // string literals being provided directly, at the usage site:
241243 static constexpr std::string_view measurement{" measurement" };
242244 static constexpr std::string_view challenger_mean{" challenger_mean" };
243245 static constexpr std::string_view challenger_stddev{
0 commit comments