Go Learning: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 8: | Line 8: | ||
=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. [[Go_Language_Error_Handling#TO_DEPLETE|Go Language Error Handling | TO DEPLETE]]. | ||
* Idiomatic documentation in Go. How do I document functions? Types? Classes? [[Go_Documentation#TO_DEPLETE|Go Documentation | TO DEPLETE]]. | |||
Revision as of 23:36, 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. Go Language Error Handling | TO DEPLETE.
- Idiomatic documentation in Go. How do I document functions? Types? Classes? Go Documentation | TO DEPLETE.