17 followers
Golang software development and training.
For information and rates: paul.digi4n@gmail.com
Subscribe to my newsletter and never miss my upcoming articles
We already discussed when to use constructors and when let the user of your library initialize their structures. The short version is that if the structure makes sense and can be used as zero value, or with some fields unset. Or, in other words, if ...
The Golang standard library comes with a simple interface, context.Context, which is a little harder to understand and use than the others. The difficulties in getting the context.Context interface may be the naming, maybe not super appropriate. In t...
Go standard library comes with a nice little structure that allows to stop long-running goroutines, when theirs result is not needed anymore: context.Context. If any of the call you are making, has the potential to block for a long amount of time, it...
In go there are two ways to create structures. Either you instantiate the structure directly, populate its fields. Or you use a constructor, that will populate the structure fields. Suppose we have a structure: type Foo struct { Fuz int Bar [...
Today I found a small mistake in our codebase. The code was like this: type Foo struct { baz []int } // ... func (f *Foo) Fun(a int) { if len(f.baz) == 0 { f.baz = []int{a} } else { f.baz = append(f.baz, a) } } Whic...
Usually when doing any IO, either over network or against disk, there are always at least two options. Execute each IO operation by itself. Execute all the IO operation together. Each of this two operation comes with tradeoffs. If you execute each ...
