Revision as of 00:45, 6 September 2023

Internal

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.
Understand why we can simply declare a struct with var, but not a map. Why do we need to make() the map?
Go_Slices#NJUL
Revisit and refactor Go_Integers#Conversion_between_bytes_and_strings
JSON_in_Go#TO_PROCESS
The difference between new() and make(). Why two?
In depth understanding of Printf() formatting options.

@@ Line 7: / Line 7: @@
 =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. <font color=darkkhaki>Continue here: [[Go_Language_Error_Handling#TO_DEPLETE]].</font>