Tracking issue for complete 32-bit support

[navaati]

There is a number of small issues making usage of the lib on 32-bit systems (such as embedded chips) impossible or limited. I’ll collate them in this issue with the relevant PRs when I or someone else tackle them, in order to avoid opening many issues but still remember the list.

• 32 bit support on mips and powerpc platforms: was already done by @chitoku-k in *: Remove AtomicU64 on unsupported platforms #42, thanks !
• 32 bit support on all platform Some 32 bit platforms are not supported #201 chore(portability): Support all platforms without 64 bit atomics #203
• u32 support for Counter: has been done by @brocaar in feat(encoding): add impls for Encode*Value #173, thanks !
• f32 support for Counter: Add support of f32 for Gauge and Counter #216
• u32 support for Gauge: was already done by @koushiro in feat(metrics): support Gauge<u32, AtomicU32> type #191, thanks !
• f32 support for Gauge: Add support of f32 for Gauge and Counter #216
• i32 support for Gauge: has been done by @brocaar in feat(encoding): add impls for Encode*Value #173, thanks !
• Histograms support for something smaller than f64: this one is not a blocker as Histograms use a RWLock rather than Atomics so it works (non-atomic f64 support is always present in Rust via emulation), but it may be slower or consume more memory than wished for

[navaati]

@mxinden One thing I’m not sure about is Examplars: I know @brocaar added support for the encoding of them in #173 but I don’t don’t think there is tests for them in 32-bit sizes or if they require Atomics, as I don’t really know how to use them. So their support status on 32-bit machines is unknown to me.