-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Go error handling best practices #94
Comments
Having coding best practices (Decred specific and linked externally) in one place would also simplify developer onboarding. |
Great idea. Considering the amount of Go code we have in the Decred project, adding a landing page for Go devs is probably a good idea. I know dcrd already has a lot of this in its README + docs, but this is applicable to all Go projects and not just that one. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
decred/dcrd#2181 captures Go error handling best practices accumulated from years of experience and discussions. This looks like valuable knowledge to start collecting in the dev docs. It would also be more safe in the devdocs repo, compared to GitHub issues (that are currently not archived by anyone afaik). As a small bonus, it would make for more "good tech read" pages available offline via Git.
The text was updated successfully, but these errors were encountered: