Is function parameter validation using errors a good pattern in Go?

Question

Is parameter validation using error return codes considered good practice ? I mean where should somebody use errors vs panics (are there any guidelines?).

For instan

Answer 1

The answer to this is subjective. Here are my thoughts:

Regarding panic, I like this quote from Go By Example (ref)

A panic typically means something went unexpectedly wrong. Mostly we use it to fail fast on errors that shouldn’t occur during normal operation, or that we aren’t prepared to handle gracefully.

In the description of your use case, I would argue that you should raise an errors and handle the errors. I would further argue that it is good practice to check the error status when one is provided by the function you are using and that the user should check if one is provided in the documentation.

Panics I would use to stop the execution if I run across an error that is returned from the function you are writing that I check and don't have a way to recover from.