Paho Lurie-Gregg

I like the idea of allowing custom types for consts-generation. I'm (slowly) rewriting dimensioned to use proc-macros, so now is probably not the best time to add it. It doesn't...

> Another problem is that it is hard to do arithmetic operations between ordered-float-si-values Is it? What issue have you been having? It seem to work fine for me: ```rust...

The easiest way to do this is to accept something that can convert into Kelvin. You will also need to call `value()` (part of trait `Dimensionless`) to get the underlying...

> But now that I think about it, if I implement the function with this trait requirement and try to write another function that uses this one, won't that requirement...

> This strategy allows for accepting a Length in any units without declaring the input units. It allows the _appearance_ of accepting a Length in any units. In reality, lengths...

Here's what that example might look like in dimensioned: ```rust use dimensioned::{si, f64prefixes::*}; fn circumference(r: si::Meter) -> si::Meter { 2.0 * r * std::f64::consts::PI } fn main() { let l1...

See also: https://github.com/paholg/dimensioned/issues/9

This is interesting. What I _really_ want is a way to customize how my types are displayed in all error messages. The potential there to make things confusing is high,...

Sorry, I guess I never noticed this issue. If you're still interested in adding derived units, you can add them to the `derived!` call in the appropriate unit system in...

Yeah, that would be ideal. I was just trying to think of a way I could do it without editing the compiler.