I guess this would be alright if you don't need to actually handle any errors and functions that you call are unrelated. If your functions return a value (that you are going to use) and an error, you probably can't just log an error and continue as that returned value is likely to be nil.
Consider:
users,err:=getUsers()iferr!=nil{// can't just log an error as the 'users' is going to be usedreturnerr}banned,err:=banUsers(users)iferr!=nil{returnerr}_,err:=unbanUSers(banned)
And in a scenario where you don't handle any errors, you can also just append them to a slice of errors and decide what you want to do with them in the end :)
Otherwise, handle errors as the official docs suggest :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I guess this would be alright if you don't need to actually handle any errors and functions that you call are unrelated. If your functions return a value (that you are going to use) and an error, you probably can't just log an error and continue as that returned value is likely to be nil.
Consider:
And in a scenario where you don't handle any errors, you can also just append them to a slice of errors and decide what you want to do with them in the end :)
Otherwise, handle errors as the official docs suggest :)