@realn2s@infosec.exchange @anderseknert@hachyderm.io @anderseknert@swecyb.com I think it’s because Err are treated like standard values in Go, meaning for lots of calls to a function you have expect 2 results, the first on is the value, the second the Err and then check if the err is null to determine whether or not there was an issue https://go.dev/blog/error-handling-and-go
Replying to
