Motivation Early on in my Go journey, I was building a billing engine. I needed to handle decimal calculations accurately. Unfortunately, Go does not have a native decimal type. After about an hour of research I found 2 error free solutions. Fast forward to Jan 2021 and a Google search for retrieves the following results: decimal handling in golang In my view, most people who contribute to open source projects are amazing and brave. It takes a lot of courage to put your work and ideas out there. My intention here is not to criticise their work. At the time this post was penned, the library mentioned in the first search result is a poor choice if you want accurate results. There are numerous open issues clearly indicating incorrect results. The second search result has an open issue for incorrect results with very large values. All the other search results are discussing various options to handle decimal operations. The motivation for this post is to discuss 2 error free options with the hope that this post reaches more gophers. Option 1 - https://github.com/cockroachdb/apd is a popular open source DB written in Go. I use it for most of my projects. I was using it for the billing engine I was building and my investigation led me to the library they were maintaining. CockroachDB Here is some example code for decimal division. make sure you are using the latest version of the library - at the time of this post. Note: v2 main ( ) { context := apd.BaseContext.WithPrecision( ) xDecimal, _, err := apd.NewFromString( ) err != {
		log.Fatalln(err)
	} yDecimal := apd.New( , )

	result := apd.New( , )

	_, err = context.Quo(result, xDecimal, yDecimal) err != {
		log.Fatalln(err)
	}

	fmt.Println(result)
} package import "fmt" "log" "github.com/cockroachdb/apd/v2" func main () // Division needs a rounding specified. // Precision here is the total number of digits // to the left and right of the decimal place. 10 // x = 1.234 "1.234" if nil // y = 3 3 0 0 0 if nil Produces the following result: 0.4113333333 Here is some example code based on discussion to control rounding. here main ( ) ( DecimalCtx = &apd.Context{
		Precision: ,
		Rounding:    apd.RoundHalfUp,
		MaxExponent: ,
		MinExponent: , Traps: apd.DefaultTraps &^ apd.InvalidOperation,
	}
) {
	xDecimal, _, _ := apd.NewFromString( ) err := LimitDecimalWidth(xDecimal, , ) err != {
		log.Println(err)
	}
	fmt.Printf( , xDecimal) yDecimal, _, _ := apd.NewFromString( )
	err = LimitDecimalWidth(yDecimal, , ) err != {
		log.Println(err)
	}
	fmt.Printf( , yDecimal)
} { d.Form != apd.Finite || precision <= { } scale < math.MinInt32+ || scale > math.MaxInt32 { errors.New( )
	} scale > precision { fmt.Errorf( , scale, precision)
	} c := DecimalCtx.WithPrecision( (precision))
	c.Traps = apd.InvalidOperation _, err := c.Quantize(d, d, - (scale)); err != { lt v := precision - scale; v { :
			lt = :
			lt = fmt.Sprintf( , v)
		} fmt.Errorf( , precision, scale, lt)
	} } package import "errors" "fmt" "log" "math" "github.com/cockroachdb/apd/v2" var // DecimalCtx is the default context for decimal operations. Any change // in the exponent limits must still guarantee a safe conversion to the // postgres binary decimal format in the wire protocol, which uses an // int16. See pgwire/types.go. 20 2000 -2000 // Don't error on invalid operation, return NaN instead. func main () "14.955" // Max 4 digits to the left and right of decimal place. Max 1 digit to right of decimal place. 4 1 if nil "x= %v\n" // Max 4 digits to the left and right of decimal place. Max 2 digits to right of decimal place. "14.955" 4 2 if nil "y= %v\n" func LimitDecimalWidth (d *apd.Decimal, precision, scale ) int error if 0 return nil // Use +1 here because it is inverted later. if 1 return "out of range" if return "scale (%d) must be between 0 and precision (%d)" // http://www.postgresql.org/docs/9.5/static/datatype-numeric.html // "If the scale of a value to be stored is greater than // the declared scale of the column, the system will round the // value to the specified number of fractional digits. Then, // if the number of digits to the left of the decimal point // exceeds the declared precision minus the declared scale, an // error is raised." uint32 if int32 nil var string switch case 0 "1" default "10^%d" return "value with precision %d, scale %d must round to an absolute value less than %s" return nil Output

x= 15.0
y= 14.96 Option 2 - Use a database Most popular databases have native support for decimal type. If your app involves the use of a database and you need to perform decimal operations on values which are already stored in the DB, then it may be convenient to use SQL to perform decimal operations instead of having to retrieve data and then perform decimal operations in Go. In the event data is not already in the DB, you can construct a SQL statement to perform decimal operations with the understanding that there is a network hop. Example SQL: // PostgreSQL ( :: / :: ):: ( , );

// CockroachDB ( :: / :: ):: ( , ); SELECT '1.234' numeric '3' numeric numeric 20 10 SELECT '1.234' decimal '3' decimal decimal 20 10 Gotchas for Option 1 You will need to spend a couple of hours learning the library. Gotchas for Option 2 A network hop is involved if decimal operations cannot be performed directly on data in the DB. It may pay to spend some time to measure this delay and then assess if option 2 fits your needs for data not already in the DB. The network hop results in a less performant solution when compared to Option 1. Setting up a DB to perform decimal operations will increase cost and complexity if your app does not need a DB. Summary 2 error free options for handling decimal types in Go have been presented. Always prototype new options to measure and understand if they can fit your needs. Trivia Did you know that the co-founder and current CEO of CockroachDB was one of the original authors of the popular tool ? Gimp Disclaimer I am not an employee of CockroachDB.

Google

Docker Images: Name Vs. Tag Vs. Digest

How to Successfully Set Up KrakenD on GKE: A Step by Step Guide

Read My Stories

Nominated for 2022 - HackerNoon Contributor of the Year - Docker

Too Long; Didn't Read

Make resilience your competitive advantage

2 Error-Free Options for Decimal handling in Golang

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

Docker Images: Name Vs. Tag Vs. Digest

104 Stories To Learn About Go

105 Stories To Learn About Functional Programming

100+ Free Pluralsight Courses to learn Python, Java, and Spring Boot

10 Websites to Learn JavaScript for Beginners

Docker Images: Name Vs. Tag Vs. Digest

104 Stories To Learn About Go

105 Stories To Learn About Functional Programming

100+ Free Pluralsight Courses to learn Python, Java, and Spring Boot

10 Websites to Learn JavaScript for Beginners

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps