Nic Holthaus

Let's replace it with 'mins' then. On Wednesday, July 25, 2018, Johel Ernesto Guerrero Peña < [email protected]> wrote: > There's an ambiguity between the min function and the min abbreviation...

I agree with the logic. v3.0 is going to have a hefty upgrade burden on the users from 2.3, but that's the price of progress. We'll need an upgrade guide...

The macros were original written, then expanded, to reduce boiler-plate solely within the library. Knowing they'd be useful to people, I documented some of them, but the work to really...

The library as a whole is over-namspaced in 2.3, in a way that breaks ADL. I think we should look at moving all non-member functions into the units namepsace, and...

@johnmcfarlane agree with you, but I think I'm missing a little context on what the two expressions you're referring to are? Might be a stretch for 3.0.0, but we (or...

So the assumption I was going off was that if conversions were implicit, that would be transparent to the user, since the final conversion is determined by the l-value type...

can you show some pseudo-code of what you'd want the duration-like interface to look like? My mind is stuck on some type of `units::quantity` which I don't really like.

This will get first class support in 3.0

I'd marked this wontfix because the issue is solved generically in the still-unreleased version 3, which I'd hoped to have released about a month ago. In v3 we support templated...

First off, congratulations on your impending publication! I hope `units` helped you, and I'm humbled if it contributed to science in any way. Assuming an IEEE-ish format, I'd recommend to...