Separator should be configurable for stringValue properties and functions

[pfei5]

The separator for the stringValue property and methods is hard-coded to a space " ".
This increases the size of the resulting string unnecessarily by something like 30%.
We have storage constraints on iOS and especially on watchOS.
IMHO the separator should be an empty string, but at the very least configurable.

Thank you for an otherwise amazingly convenient and tidy library.

[orchetect]

Yes there's a few missing customization points that would be worth adding including these.

I can push a release fairly soon since they would mostly be defaulted parameters so it shouldn't be code-breaking.

The stringValue property on Collection must remain with a hard-coded space since a collection may be of any integer size (8-bit, 16-bit, 32-bit, or 64-bit) and the separator is needed to differentiate values. This is a convenience property and that is the most common use case.

For customized output, the stringValue(...) methods with an added separator parameter would make it easy to override it with an empty separator. The separator parameter should remain defaulted to a space (" ") for consistency and for the same consideration of varying integer sizes.

[Proper-Job]

Wow, that's great, thank you so much!

[orchetect]

Release 1.3.0 includes the changes. Let me know if that works for you.