Giters
uber-go
/
guide
The Uber Go Style Guide.
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
15308
Watchers:
231
Issues:
67
Forks:
1685
uber-go/guide Issues
Verify Interface Compliance with Generic support
Updated
3 months ago
Translate this Guide to Deutsch
Updated
3 months ago
Comments count
2
Update links to Go packages/wiki
Closed
4 months ago
Add information about github.com/pkg/errors
Updated
6 months ago
Comments count
2
style.md#errors - Nesting can be removed in example of Error Types section
Updated
6 months ago
Uber Go Style Guide
Closed
8 months ago
Question: how to use custom logger with the guide 'Exit-Once'
Closed
10 months ago
Error Handling Approaches Discussion
Updated
10 months ago
Releases for Watch Notifications
Closed
a year ago
Comments count
2
Proposal: prefer `%q` to format strings over `%s`
Updated
a year ago
Comments count
1
proposal: table test guidance is too prescriptive
Closed
a year ago
Comments count
3
Guideline: Don't Log and Return Errors
Closed
a year ago
Comments count
2
proposal: Avoid calling methods on map value, e.g. m[key].Method()
Updated
a year ago
Comments count
1
Misleading formulation in "Receivers and Interfaces"
Closed
a year ago
Comments count
1
Proposal: Note that VS Code and GoLand have provided “inlay hints” that can avoid naked parameters
Updated
a year ago
Comments count
3
style: Linting the style.md with `markdownlint`
Closed
a year ago
Proposal: Avoid stuttering in naming
Updated
2 years ago
Proposal: Add Type Parameters ( Generics )
Closed
2 years ago
Comments count
2
About updating uber-go-style-guide-kr
Closed
2 years ago
Comments count
2
Uber Go style should clarify ordering for type declarations and methods in files with multiple types
Updated
2 years ago
Comments count
8
The style guide should include canonical example file(s)
Closed
2 years ago
Comments count
1
Possible issue with testing code
Closed
2 years ago
Comments count
1
Proposal: Discourage taking an address of empty structs
Updated
2 years ago
Comments count
2
Discuss: should we provide guidance on function arguments being functions
Closed
4 years ago
Comments count
9
Some guidelines in "Error Types" and "Error Wrapping" are incorrect
Closed
3 years ago
Comments count
5
Line length soft limit
Closed
3 years ago
Proposal: Prefer interfaces to function references
Updated
3 years ago
Comments count
7
Proposal: Avoid blocking sends to a channel without timeout
Updated
3 years ago
Comments count
8
"Channel size is one or none" forbids common and useful patterns
Updated
3 years ago
Comments count
5
Embedding a sync.Mutex is equally bad whether or not the type is exported
Closed
3 years ago
Comments count
3
Uber
Closed
3 years ago
Comments count
1
Guideline: One log.Fatal per application
Closed
3 years ago
Comments count
1
Initialization of fields with zero values
Closed
3 years ago
Comments count
2
Proposal: Export fields and methods of unexported types
Updated
3 years ago
Wrong link for the go common mistakes guide
Closed
3 years ago
one more comma
Closed
3 years ago
Comments count
1
Add some guides of writing go test
Updated
3 years ago
Recommended Linters?
Closed
4 years ago
'Import Aliasing' is good for long name of package
Closed
4 years ago
Comments count
1
Guideline: Pointers to Interfaces
Closed
4 years ago
Comments count
1
Invalid link in `Initializing Maps`
Closed
4 years ago
Guideline: error handling and plumbing
Closed
4 years ago
Guideline: Avoid init
Closed
4 years ago
Comments count
2
Guideline: Avoid fields or variables named after built-in types
Closed
4 years ago
"nil is a valid slice" issue
Closed
4 years ago
Comments count
2
Possible typo?
Closed
4 years ago
Comments count
1
Guideline: For functional options, don't recommend closures
Closed
4 years ago
Comments count
4
Error Types, Error Wrapping: Go1.13 Errors
Closed
5 years ago
Comments count
1
very good project!
Closed
5 years ago
Comments count
1
The zero value (a slice declared with var) is usabe... is missleading (could panic)
Closed
5 years ago
Comments count
2
Previous
Next