Open mkalte666 opened 8 months ago
I don't think the trait is necessary. Similar to how how methods for other underlying types are implemented, we would just need to add methods for Complex
to return the re
/im
fields.
e.g. is_nan
for floating point types:
https://github.com/iliekturtles/uom/blob/85b665e8e574ff9b5ab91163f5b95c0e10412b9b/src/system.rs#L759-L780
oh sorry I should have clarified this; im using the trait because I don't wanna keep track of(rather, don't have the time for) more patching right now. Basically a quick and dirty way to get this to work for me right now without much thought^^
A solution like you described would be much preferable :D
Maybe I can get to that as well later, but right now I'm quite busy in way to may ways ;_;
It can be interesting (or needed) to access only the real or imaginary part of a complex quantity.
Currently, i have solved this for my codebase like this, but it would be nice to have this available in uom directly as well. For all i know, its already there; im known to miss the most obvious functions out there :D
Example usage would be somthing like this: