Error strings should start with a lowercase letter and not end with punctuation. They should state what went wrong in a concise, factual manner (for example, "file not found", not "File not found!").
Following Go conventions for error messages ensures that errors are consistent and can be combined in sentences. A lowercase, unpunctuated error string fits naturally when wrapped or printed, and maintains readability across the codebase.
Side-by-side examples engineers can pattern-match during review.
err := errors.New("File Not Found!")err := errors.New("file not found")err := errors.New("File Not Found!")err := errors.New("file not found")From the same buckets as this rule.
Check if loops use equality operators (== or !=) in termination conditions. These can lead to infinite loops if the condition is never met exactly. Instead, use relational operators like < or > for safer loop termination.