Question 1

How do I round a number using udecimal?

Accepted Answer

Use methods like RoundBank, RoundAwayFromZero, or RoundHAZ after operations, as shown in the usage examples. You must explicitly call these since udecimal truncates extra digits by default to avoid implicit rounding errors.

Question 2

Is udecimal faster than shopspring/decimal?

Accepted Answer

Yes, benchmarks in the README indicate udecimal is 5x to 20x faster than shopspring/decimal due to its fixed-point design and zero-allocation optimizations. However, this speed comes with the trade-off of limited precision to 19 decimal places.

Question 3

Does udecimal allocate memory during operations?

Accepted Answer

It aims for 99% zero allocation by using a 128-bit integer, but in rare overflow cases, it falls back to big.Int which allocates memory. This is detailed in the 'How it works' section, where most financial applications stay within the 128-bit range.

Question 4

What rounding methods does udecimal support?

Accepted Answer

It supports Banker's rounding, HALF AWAY FROM ZERO, HALF TOWARD ZERO, and AWAY FROM ZERO, as listed in the features. Each must be explicitly invoked to ensure correct financial calculations.

Question 5

Can I use udecimal for arbitrary precision decimals?

Accepted Answer

No, udecimal is fixed-point with up to 19 decimal places, so it's not suitable for arbitrary precision. The README compares it to libraries like shopspring/decimal which offer arbitrary precision but at a performance cost.

Question 6

Is udecimal thread-safe for concurrent calculations?

Accepted Answer

Yes, all operations return new Decimal values, making it concurrent-safe for sharing across goroutines. This is a key feature highlighted for financial applications needing reliability in multi-threaded environments.

udecimal

What is udecimal?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions