You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The correct way to modify issues is to assign the new value to it:
issues = issues.AddError("error")
During development, I have occasionally written the former. Tests should help catch changes that are accidentally introduced, but it would be nice to catch modified Issues that are never used.
It would be nice to have an "unused result" warning (similar to "unused variable") at compile or test time.
I'mma look into go vet.
The text was updated successfully, but these errors were encountered:
The following has no side effects:
The correct way to modify
issues
is to assign the new value to it:During development, I have occasionally written the former. Tests should help catch changes that are accidentally introduced, but it would be nice to catch modified
Issues
that are never used.It would be nice to have an "unused result" warning (similar to "unused variable") at compile or test time.
I'mma look into
go vet
.The text was updated successfully, but these errors were encountered: