Nick

@mborland : Just tried to build the docs; got the following error: ``` sf/number_series.qbk:325: error: Mismatched [endsect] near column 9. ```

@mborland : Very cool; here's the comparison to Kim Walish's sieve: ```cpp #include #include #include #include template void prime_sieve(benchmark::State& state) { Z upper = static_cast(state.range(0)); for(auto _ : state) {...

If the values were printed as hexfloat as well, the issue would be moot: ``` C:/projects/arrow/cpp/src/arrow/util/decimal_test.cc(557): error: Expected equality of these values: dec.ToReal(scale) Which is: 1e-163 = 0x1.708d0f84d3de7p-542 expected Which...

@phonetagger: Yup, the only robust solution here is hexfloat printing.

> Most people wouldn't be happy to have to convert from hexfloat to a format they can actually work with. Just print both formats.

Diff to fix: ``` diff --git a/googletest/include/gtest/gtest.h b/googletest/include/gtest/gtest.h index 04a84f32..02fb4d36 100644 --- a/googletest/include/gtest/gtest.h +++ b/googletest/include/gtest/gtest.h @@ -1572,11 +1572,11 @@ AssertionResult CmpHelperFloatingPointEQ(const char* lhs_expression, ::std::stringstream lhs_ss; lhs_ss

@dominichamon : This particular case that inspired the issue is when user-supplied datasets are parametrized as inputs to `google/benchmarks`. The data flows through a lot of potential benchmarks; but not...

> Should we add a similar feature to the 2.0 framework? It appears this library is targeting application developers. But if I'm not mistaken, a requirement to standardize is the...

> This actually is not the requirement of the standardization process. Fair enough, but this is certainly a desiderata. > Why dimensionless is special here? My context for the discussion...

So even if I use this file, I still have a problem that I cannot write generic code which works with both `double` and `mp-units`: ``` math/include/boost/math/optimization/random_search.hpp:108:62: fatal error: no...