Our great sponsors
guide | errors | |
---|---|---|
26 | 30 | |
15,218 | 7,511 | |
2.0% | - | |
5.2 | 0.2 | |
26 days ago | over 2 years ago | |
Makefile | Go | |
Apache License 2.0 | BSD 2-clause "Simplified" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
guide
- I write HTTP services in Go after 13 years (Mat Ryer, 2024)
- Uber Go Style Guide
-
Thursday Daily Thread: Python Careers, Courses, and Furthering Education!
I'm pumped to learn Python. Are there any learning tools or docs I should focus on? For Go I liked the Uber Go Style Guide which represents a modern and idiomatic approach to Go and is a good tour of the language itself (for experienced engineers.) Is there something similar for Python?
- Course recommendation
- Is there a good place to find best practices?
-
Senior engineer here trying to pick up Go for jobs. What resources can you recommend me to cover as much ground as possible
https://github.com/uber-go/guide/blob/master/style.md - must have, write good go code from the beginning.
- Google’s Go Style Guide
-
Feedback for my first code
I really recommend reading: - Effective Go: https://go.dev/doc/effective_go#errors - Style Guide(by Uber): https://github.com/uber-go/guide/blob/master/style.md
-
Development guidelines
As you see - there are no reference to any technology or framework. There are a lot of best-practices for almost any framework, so you can choose an appropriate one. For example - if you're a rails developer, then you can check https://github.com/rubocop/ruby-style-guide and https://github.com/rubocop/rails-style-guide but if you're a golang developer - https://github.com/uber-go/guide/blob/master/style.md and https://developers.mattermost.com/contribute/more-info/server/style-guide/
-
[Beginner]How to structure my project with module and package?
Read ubers style guide first, its good to have some base rules that you follow when beggining. Heres the link: https://github.com/uber-go/guide/blob/master/style.md.
errors
-
Show HN: Error return traces for Go, inspired by Zig
Can you explain why we should this over https://github.com/pkg/errors?
-
Cant wait for less verbose error handling
The pkg/errors package offers some nice add-ons for easier error handling. Too bad it was put into maintenance mode pending whatever changes/improvements are coming in Go 2.
- Error handling and serializing
-
isse for go path in neovim
I can't figure out the issue so here for some help, I am using `neovim/nvim-lspconfig` my `gopls` doesn't recognise external paths such as `github.com/pkg/errors` , it throws error`could not import github.com/pkg/errors (cannot find package "github.com/pkg/errors" in any of /usr/local/go/src/github.com/pkg/errors (from $GOROOT) /Users/ra compiler (BrokenImport)\`
-
What am I supposed to be doing with errors?
Also - there are some error handling utils that allow you to wrap errors before passing: https://github.com/pkg/errors
-
Go error handling is not verbose but the error handling itself.
Should've been something like errors.Newf("failed to foofoo %s", foo) instead and preferably never invent %w but have some controlled way to wrap like errors.Wrapf(err, "failed to foofoo %s", foo) that was in ye olde github.com/pkg/errors.
-
How to wrap the error best?
Prefer using errors.Wrap and errors.Wrapf from https://github.com/pkg/errors . It's frozen because they don't want to add features, waiting for a re-write of error handling in Go2.
- mdobak/go-xerrors: Yet another error handling library.
-
Getting at the type of error after it has been wrapped with errors.Wrap
Im using zerolog and in order to get the stack trace for my error I have to wrap my error in errors.Wrap from "github.com/pkg/errors".
-
When ia a good time to panic?
And for "real programs" you can use https://github.com/pkg/errors (if you want stack traces)
What are some alternatives?
uber-go-style-guide-th - Uber's Go Style Guide Translation in Thai. Linked to the uber-go/guide as a part of contributions https://github.com/uber-go/guide
zerolog - Zero Allocation JSON Logger
uber-go-style-guide-kr - Uber's Go Style Guide Official Translation in Korean. Linked to the uber-go/guide as a part of contributions
autoflags - Populate go command line app flags from config struct
golang-standards/project-layout - Standard Go Project Layout
go-multierror - A Go (golang) package for representing a list of errors as a single error.
awesome-linux-containers - A curated list of awesome Linux Containers frameworks, libraries and software
logrus - Structured, pluggable logging for Go.
ireturn - Accept Interfaces, Return Concrete Types
bitio - Optimized bit-level Reader and Writer for Go.
automaxprocs - Automatically set GOMAXPROCS to match Linux container CPU quota.
Testify - A toolkit with common assertions and mocks that plays nicely with the standard library