Go Learning: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 13: | Line 13: | ||
* Initialization Second Pass | * Initialization Second Pass | ||
** Understand why we can simply declare a struct with var, but not a map. Why do we need to make() the map? | ** Understand why we can simply declare a struct with var, but not a map. Why do we need to make() the map? | ||
** The difference between new() and make(). Why two? | ** The difference between new() and make(). Why two? How about the <code>.New()</code> functions. | ||
* 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]] | ||
* Idiomatic documentation in Go. How do I document functions? Types? Classes? <font color=darkkhaki>Continue here: [[Go_Documentation#TO_DEPLETE]].</font> | * Idiomatic documentation in Go. How do I document functions? Types? Classes? <font color=darkkhaki>Continue here: [[Go_Documentation#TO_DEPLETE]].</font> |
Revision as of 23:16, 6 September 2023
Internal
Current Book
- Microservices with Go. Building scalable and reliable microservices with Go by Alexander Shuiskov
Books
- The Go Programming Language by Alan A. A. Donovan, Brian W. Kernighan
- Efficient Go by Bartlomiej Plotka
Subjects
- Errors: Go_Language_Error_Handling#TODO
- Blend https://go.dev/doc/effective_go + https://github.com/golang/go/wiki/CodeReviewComments into Go. Many answers to my questions may already be in there.
- Initialization Second Pass
- Understand why we can simply declare a struct with var, but not a map. Why do we need to make() the map?
- The difference between new() and make(). Why two? How about the
.New()
functions.
- De-khaki first-iteration Go pages. Start here Go_Language#TO_DEPLETE_and_MERGE_into_THIS_DOCUMENT
- 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.
- Go_Slices#NJUL
- Revisit and refactor Go_Integers#Conversion_between_bytes_and_strings
- JSON_in_Go#TO_PROCESS
- In depth understanding of Printf() formatting options.
- Go_Concepts_-_Operators
- Go_Concepts_-_Functions, Go_Closures
- Go_Concepts_-_The_Type_System
- Go_for
- Go_Concepts_-_Lexical_Structure
- Go_Keyword_import
- Go Concepts - Templates
- Go Concepts - Compiler
- Go Concepts - Limitations
- Go_Operations_TO_DELETE
Articles
- https://yourbasic.org/golang/advantages-over-java-python/
- https://thenewstack.io/rust-vs-go-why-theyre-better-together/
- https://www.infoq.com/presentations/go-iron-production/
- Go for Java Programmers https://www.youtube.com/watch?v=_c_tQ6_3cCg
- https://astaxie.gitbooks.io/build-web-application-with-golang/content/en/index.html