Go Learning: Difference between revisions
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
=Subjects= | =Subjects= | ||
* Go had no exceptions, what is the idiomatic way to handle errors? Handling errors after each function call seems noisy. [[Go_Language_Error_Handling#TO_DEPLETE|Go Language Error Handling | TO DEPLETE]]. | * Go had no exceptions, what is the idiomatic way to handle errors? Handling errors after each function call seems noisy. <font color=darkkhaki>Continue here: [[Go_Language_Error_Handling#TO_DEPLETE|Go Language Error Handling | TO DEPLETE]].</font> | ||
* Idiomatic documentation in Go. How do I document functions? Types? Classes? [[Go_Documentation#TO_DEPLETE|Go Documentation | TO DEPLETE]]. | * Idiomatic documentation in Go. How do I document functions? Types? Classes? <font color=darkkhaki>Continue here: [[Go_Documentation#TO_DEPLETE|Go Documentation | TO DEPLETE]].</font> | ||
* Packages | |||
** Understand package names like encoding/json. What is the underlying structure that result is such a naming scheme? | |||
** Continue here: | |||
Revision as of 23:38, 5 September 2023
Internal
Books
- Microservices with Go. Building scalable and reliable microservices with Go by Alexander Shuiskov
- The Go Programming Language by Alan A. A. Donovan, Brian W. Kernighan
- Efficient Go by Bartlomiej Plotka
Subjects
- Go had no exceptions, what is the idiomatic way to handle errors? Handling errors after each function call seems noisy. Continue here: Go Language Error Handling | TO DEPLETE.
- Idiomatic documentation in Go. How do I document functions? Types? Classes? Continue here: Go Documentation | TO DEPLETE.
- Packages
- Understand package names like encoding/json. What is the underlying structure that result is such a naming scheme?
- Continue here: