Quantity-Aware access parts of quantity with complex storage type

[mkalte666]

Quantity-Aware access parts of quantity with complex storage type

[iliekturtles]

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:

uom/src/system.rs

Lines 759 to 780 in 85b665e

	// Explicitly definte floating point methods for float and complex storage types.
	// `Complex<T>` doesn't implement `Float`/`FloatCore`, but it does implement these methods
	// when the underlying type, `T`, implements `FloatCore`.
	mod float {
	storage_types! {
	types: Float, Complex;
	use super::super::*;
	impl<D, U> Quantity<D, U, V>
	where
	D: Dimension + ?Sized,
	U: Units<V> + ?Sized,
	{
	/// Returns `true` if this value is `NAN` and `false` otherwise.
	#[cfg_attr(feature = "cargo-clippy", allow(clippy::wrong_self_convention))]
	#[must_use = "method returns a new number and does not mutate the original value"]
	#[inline(always)]
	pub fn is_nan(self) -> bool
	{
	self.value.is_nan()
	}

[mkalte666]

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 ;_;