wneessen/decimal
1
1
Fork 0
mirror of https://github.com/shopspring/decimal.git synced 2024-11-23 04:40:49 +01:00
Code Issues Projects Releases Packages Wiki Activity

README: Fix URLs for the official Go pages

Browse source
This commit is contained in:
Ryoya Sekino 2021-11-26 13:50:41 +09:00 committed by GitHub
parent fa3b22f4d4
commit 39639f86d8
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
README.md
View file

@ -1,6 +1,6 @@
# decimal # decimal
[![Build Status](https://app.travis-ci.com/shopspring/decimal.svg?branch=master)](https://app.travis-ci.com/shopspring/decimal) [![GoDoc](https://godoc.org/github.com/shopspring/decimal?status.svg)](https://godoc.org/github.com/shopspring/decimal) [![Go Report Card](https://goreportcard.com/badge/github.com/shopspring/decimal)](https://goreportcard.com/report/github.com/shopspring/decimal) [![Build Status](https://app.travis-ci.com/shopspring/decimal.svg?branch=master)](https://app.travis-ci.com/shopspring/decimal) [![GoDoc](https://pkg.go.dev/badge/github.com/shopspring/decimal)](https://pkg.go.dev/github.com/shopspring/decimal) [![Go Report Card](https://goreportcard.com/badge/github.com/shopspring/decimal)](https://goreportcard.com/report/github.com/shopspring/decimal)
Arbitrary-precision fixed-point decimal numbers in go. Arbitrary-precision fixed-point decimal numbers in go.
@ -59,7 +59,7 @@ func main() {
## Documentation ## Documentation
http://godoc.org/github.com/shopspring/decimal https://pkg.go.dev/github.com/shopspring/decimal
## Production Usage ## Production Usage
@ -73,7 +73,7 @@ http://godoc.org/github.com/shopspring/decimal
Because float64 (or any binary floating point type, actually) can't represent Because float64 (or any binary floating point type, actually) can't represent
numbers such as `0.1` exactly. numbers such as `0.1` exactly.
Consider this code: http://play.golang.org/p/TQBd4yJe6B You might expect that Consider this code: https://go.dev/play/p/TQBd4yJe6B You might expect that
it prints out `10`, but it actually prints `9.999999999999831`. Over time, it prints out `10`, but it actually prints `9.999999999999831`. Over time,
these small errors can really add up! these small errors can really add up!
@ -88,7 +88,7 @@ out, the string output has to stop somewhere (let's say it stops at 3 decimal
digits, for simplicity), so you'll get 0.333, 0.333, and 0.333. But where did digits, for simplicity), so you'll get 0.333, 0.333, and 0.333. But where did
the other 0.001 go? the other 0.001 go?
Here's the above example as code: http://play.golang.org/p/lCZZs0w9KE Here's the above example as code: https://go.dev/play/p/lCZZs0w9KE
With Decimal, the strings being printed out represent the number exactly. So, With Decimal, the strings being printed out represent the number exactly. So,
if you have `x = y = 1/3` (with precision 3), they will actually be equal to if you have `x = y = 1/3` (with precision 3), they will actually be equal to
@ -113,7 +113,7 @@ modifies `a` and sets `z` as an alias for `a`, which they might not expect. It
also modifies any other aliases to `a`. also modifies any other aliases to `a`.
Here's an example of the subtle bugs you can introduce with big.Int's API: Here's an example of the subtle bugs you can introduce with big.Int's API:
https://play.golang.org/p/x2R_78pa8r https://go.dev/play/p/x2R_78pa8r
In contrast, it's difficult to make such mistakes with decimal. Decimals In contrast, it's difficult to make such mistakes with decimal. Decimals
behave like other go numbers types: even though `a = b` will not deep copy behave like other go numbers types: even though `a = b` will not deep copy