Go Learning: Difference between revisions
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
=Subjects= | =Subjects= | ||
* Probably don’t need [[Go_Language_Concurrency]] , replace it with [[Go_Language_Goroutines]] | |||
* De-khaki first-iteration Go pages. Start here [[Go_Language#TO_DEPLETE_and_MERGE_into_THIS_DOCUMENT]] | * De-khaki first-iteration Go pages. Start here [[Go_Language#TO_DEPLETE_and_MERGE_into_THIS_DOCUMENT]] | ||
* 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]].</font> | * 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]].</font> | ||
Revision as of 23:45, 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
- Probably don’t need Go_Language_Concurrency , replace it with Go_Language_Goroutines
- De-khaki first-iteration Go pages. Start here Go_Language#TO_DEPLETE_and_MERGE_into_THIS_DOCUMENT
- 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: Go_Language_Modularization#TODO.