Consider other Value primitive variants about valuable

[KevinMGranger]

I would find special-casing &[u8] (and Vec<u8>) useful in the library I'm working on.

Another (more general) idea is to do something akin to #[serde(with = "module")], allowing a customized Valuable impl on a per-field basis.

[hawkw]

tracing 0.1 supports f64s as typed values; if we're going to do a wholesale replacement of tracing's value system with valuable in tracing 0.2, we should probably add support for floats as primitive values.

[taiki-e]

we should probably add support for floats as primitive values.

I believe floats are already supported.

valuable/valuable/src/value.rs

Lines 137 to 157 in acd1a7e

	/// A Rust `f32` value
	///
	/// # Examples
	///
	/// ```
	/// use valuable::Value;
	///
	/// let v = Value::F32(3.1415);
	/// ```
	F32(f32),
	/// A Rust `f64` value
	///
	/// # Examples
	///
	/// ```
	/// use valuable::Value;
	///
	/// let v = Value::F64(3.1415);
	/// ```
	F64(f64),

[hawkw]

we should probably add support for floats as primitive values.

I believe floats are already supported.

valuable/valuable/src/value.rs

Lines 137 to 157 in acd1a7e

	/// A Rust `f32` value
	///
	/// # Examples
	///
	/// ```
	/// use valuable::Value;
	///
	/// let v = Value::F32(3.1415);
	/// ```
	F32(f32),
	/// A Rust `f64` value
	///
	/// # Examples
	///
	/// ```
	/// use valuable::Value;
	///
	/// let v = Value::F64(3.1415);
	/// ```
	F64(f64),

whoops, it looks like i can't read! never mind!

[hawkw]

I don't think this needs to be a blocker for 0.1; we can always add new primitives in backwards-compatible changes.