What are your strategies to prevent nil pointers errors in your code base?

• gofuzz

  3 1,478 0.0 Go

  Discontinued Fuzz testing for go.

  

Also, with some of the fuzzers available, you can actually generate structs and specify the nil chance like https://github.com/google/gofuzz

• go-tools

  19 5,910 7.9 Go

  Staticcheck - The advanced Go linter

Unfortunately I don't know of any tools that can/do always detect it. There's this discussion for the staticcheck linter where they basically don't think it's worth false positives in order to support it a lint for it.

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• truthy

  6 33 0.0 Go

  Package truthy provides truthy condition testing with Go generics (by earthboundkid)

I personally always make sure that, if I have a function that creates the struct, I define all of the fields. When I don't a) have control over that or b) have a function to init the struct, I typically end up using a new package called truthy that is built on generics and tells me the truthy value of the variable, kind of like Boolean(value) in javascript.

Suggest a related project