Scott P. Jones

Yes, it would also be nice to be able to correctly handle European formatting of numbers, using `,` instead of `.` for the decimal point, and `.` as the thousands...

Have you looked at [Format](https://github.com/JuliaString/Format.jl)? It is based off of `Formatting.jl` (there was a period where `Formatting.jl` was still in a personal repo, and was not getting maintained much, so...

I've concentrated more on the C format side of the package, as that is what I mostly use. These days I'm spending more time with Python code (rewriting Numpy code...

It is being maintained, although it is not currently registered.

I agree, however, it would be good to measure only lines with code on them, not whitespace, documentation strings or just comments, to not penalize people who actually try to...

What are the next steps to get this merged? I don't know why they codecov checks have failed, because there should be no change in coverage at all, since it...

What about support for DECIMAL and NUMERIC types? (up to a point, IEEE decimal floating point formats could be used, using `DecFP.jl` could support up to 34 digits (with `Dec128`),...

Oracle internal number types encode the value so that they can be compared numerically, simply by doing string (byte) comparisons (this is a common technique, that I've used in the...

You could make a Julia type that directly stores the value (maybe as a 24 or 32 byte bitstype, which would probably be the most compact way of storing the...

The reason a fixed size might be better, is that using something like `Vector` will use a lot more memory than simply using a fixed size of 24 bytes (you...