Chip Hogg

Let users set the displayed time range

2

I use perfetto to iterate on improving C++ compile times for individual files. It would be really satisfying to be able to see the "jump" once I finally break through...

Here are some options for spelling this now: ```cpp using NanoSecondsSquared = decltype(squared(Nano{})); using NanoSecondsSquared = UnitPowerT; using NanoSecondsSquared = Squared; ``` The first two are available today. The third...

Separate risk checks for overflow and truncation

1

Given a conversion from one (unit, rep) to another, we should reason separately about overflow and truncation risks. This will pave the way for new APIs in #122.

Our initial implementation for #110 will have separate checks for each of 3 stages: static cast to common type, unit conversion, and static cast to destination type. Really, there should...

We should have very high coverage, but it would be far better to _measure_ it. I'd like to have a CI job that shows the coverage after each commit.

Collect all scale factors for a unit

1

We have anonymous scaled units, which don't get a special name, but do get an automatic label which is just that scale factor plus the unscaled unit's symbol. In these...

Add runtime conversion checkers for QuantityPoint

1

I sort of forgot to do this for #110.

All I really want is negative constants. I've previously [argued at length](https://github.com/mpusz/mp-units/issues/510) that we _probably_ don't want negative _units_, and _definitely_ don't want negative _magnitudes_. In terms of the perfect...

Consider this test, from `:quantity_point_test`: ```cpp TEST(QuantityPoint, CommonPointUnitLabel) { EXPECT_THAT(stream_to_string(celsius_pt(0) - kelvins_pt(0)), AnyOf(StrEq("5463 EQUIV{[(1 / 20) K], [(1 / 20) degC]}"), StrEq("5463 EQUIV{[(1 / 20) degC], [(1 / 20) K]}")));...

Add 200-level tutorials

4

- [ ] 201: Results of unit computations - [ ] 202: Common units - [ ] 203: Magnitudes