Go (Fundamentals) 101 Update History

v1.20.a (2023/Feb/01)

• Go 1.20 started to support slice to array conversions.
• Go 1.20 added three new functions in the "unsafe" package: SliceData, String, and StringData.
• Since Go 1.20, the global random generator in the math/rand package will be auto seeded.
• mentions that -gcflags="-d=ssa/check_bce" doesn't work for some generic functions in the Bounds Check Elimination chapter.

v1.19.a (2022/Aug/29)

• Go 1.19 added some atomic types.
• Go 1.19 updated memory order guarantees.

v1.18.a (2022/Apr/06)

• Go 1.18 added custom generics support. Several articles in Go 101 are adjusted accordingly, mainly including
  • Interfaces in Go
  • Go Type System Overview (note that the "named type" terminology was added back).

v1.17.b (2021/Sep/10)

• improve implicit method value evaluation explanations. Read this and this for details.

1.16.b (2021/May/18)

• add Go 1.17 contents

1.16.a (2021/Feb/18)

• support Go 1.16 embedding feature.

1.15.b (2020/Oct/09)

• describe more about reflect.DeepEqual related details.
• add a new syntax execption.

1.15.a (2020/Aug/07)

• point out that, since Go Toolchain 1.15, using make+copy to clone slices is always more efficient than using append to clone.

1.14.g (2020/Jun/12)

• remove the new detail added in 1.14.e: The behavior of comparing struct values with both comparable and incomparable fields or array values with both comparable and incomparable elements is unspecified. The reason is the behavior will be specified.
• add a new detail: About the impossible to-interface assertions which can be detected at compile time.

1.14.f (2020/Jun/02)

• All "Go SDK" uses are changed to "Go Toolchain".

1.14.e (2020/May/06)

• add a new detail: The behavior of comparing struct values with both comparable and incomparable fields or array values with both comparable and incomparable elements is unspecified.
• add a new detail: In struct value comparisons, blank fields will be ignored.

1.14.d (2020/Apr/25)

• runtime.KeepAlive related concents are removed from Unsafe Pointers article. I'm sorry for spreading some wrong information in this article before.

1.13.i (2019/Oct/31)

• fix a bug in the example code in the Delete a segment of slice elements section of the "Arrays, Slices and Maps in Go" article.
• correct explainations in The Evaluation Moment of Deferred Function Values.
• the article "The Right Places to Call the Built-in recover Function" is renamed to "Explain Panic/Recover Mechanism in Detail". It was almost wholly re-written.

1.13.h (2019/Oct/18)

• correct the explanations for the Evaluation and Assignment Orders in Assignment Statements section in the "Expression Evaluation Orders" article.
• add two new summaries.

1.13.e (2019/Oct/07)

• I decided to withdraw the last erratum in 1.13.d. (Re-added in 1.14.d)

1.13.d (2019/Sep/30)

• add a new fact to the "type-unsafe pointers" article and pointed out a serious mistake was made in this article.

1.13.c (2019/Sep/25)

• remove the section containing a stupid code mistake from the "The Right Places to Call the recover Function" article.

1.13.b (2019/Sep/19)

• remove the inaccurate description "the address of a variable will never change"

1.13.a (2019/Sep/05)

• Go 1.13 ready.
• add two situations in the article How to Gracefully Close Channels.
• the "named type" and "unnamed type" terminologies are added back, but they are eqivalent to "defined type" and "non-defined type" now.

1.12.d (2019/May/18)

• enrich the Package-level Variables Initialization Order section.

1.12.c (2019/April/09)

• remove the "named type" and "unnamed type" terminology.
• adjust some discriptions in Type Embdding.

1.12.b (2019/April/06)

• add a Package-level Variables Initialization Order section.

1.12.a (2019/March/02)

• Go 1.12 ready.

1.11.f (2019/Jan/02)

• remove "Unused Variables" from Syntax/Semantics Exceptions In Go.

1.11.g (2018/Dec/27)

• a serious mistake was just fixed in this book. Before, the book said the starting index in a subslice syntax can't be larger than the length of the base slice. This is wrong. Please read the corrected section again for details.

1.11.f (2018/Nov/09)

• rearrange Go Details 101, more details are added.

1.11.e (2018/Oct/26)

• published Evaluation Orders.
• modify some descriptions for program resource initialization order

1.11.d (2018/Oct/18)

• remove "Comparing Interface Values" from Syntax/Semantics Exceptions In Go.
• add "Comparisons 2" to Syntax/Semantics Exceptions In Go.
• modify some descriptions for
  • comparison rules
  • package hierarchy

1.11.c (2018/Sep/22)

• add a new tip How to make a struct type incomparable?.
• add a new tip Try to reset pointers in freed-up slice elements.
• add a new tip Make optimizations by using BCE.
• remove "Precedences Of Unary Operators" from Syntax/Semantics Exceptions In Go.

1.11.b (2018/Sep/09)

• published Go Tips 101.

1.11.a (2018/Sep/01)

• mention 1.11 new wasm GOARCH in More Go Related Knowledges.
• mention 1.11 new go mod command in The Go Toolchain.

1.10.g (2018/Jun/02)

• published About Go 101.
• published Acknowledgments.

1.10.f (2018/May/15)

• published Relections in Go.
• added a channel use case: rate limiting.

1.10.e (2018/Apr/28)

• added a new detail: Exit a program with a os.Exit function call and exit a goroutine with a runtime.Goexit function call..

1.10.d (2018/Apr/18)

• added a new detail: Non-exported method names and struct field names from different packages are viewed as diffferent names..
• added a FAQ question: [What does the compiler error message declared and not used mean?](https://go101.org/article/unofficial-faq.html#error-declared-not-used")
• added a FAQ question: What is the difference between the function call time.Sleep(d) and the channel receive operation <-time.After(d)?
• added a FAQ question: What is the difference between the random numbers produced by the math/rand standard package and the crypto/rand standard package?
• added a FAQ question: What are the differences between the fmt.Print and fmt.Println functions?
• added a FAQ question: What are the differences between the built-in print/println functions and the corresponding print functions in the fmt and log standard packages?
• added a FAQ question: Why isn't there a math.Round function?
• added a FAQ question: What does the word gopher mean in Go community?

1.10.c (2018/Apr/14)

• finished the article some common concurrent programming mistakes.
• published Go details 101.
• unhid Go FAQ 101.

1.10.b (2018/Apr/06)

• added an interesting type embedding example
• mentioned receive-only channels can't be closed
• mentioned indexes in array and slice composite literals must be constants

1.10.a (2018/Mar/31)

First release, though some articles are still not finished.