Home

Index:

• Slices related:
  • How to perfectly clone a slice?
  • How to efficiently clone a slice?
  • There is not a perfect way to clone slices in Go.
  • When inserting slice elements, to get the best efficiency, it is best not to use the builtin append function.
  • Go is not C, so there is not an extreme fast way to merge slices.
  • Some details about byte slices and rune slices in Go.
  • The capacity of the result byte (or rune) slice of a conversion from a string is unspecified.
  • The support of builtin slice manipulations in Go is incomplete.
  • Three index slice uses are often verbose.
• Assignments related:
  • Some evaluation orders in multi value assignments are unspecified.
  • An ambiguity of (or dispute on) the evaluation order of LHS (left hand side) items in a multi value assignment.
  • Why Go supports multi value assignments and the influences of this decision.
  • A proposal to make Go simpler by removing the := redeclaration syntax.
• Personal opinions:
  • About the terminology "reference type" in Go.
  • The main sell point of Go is not simplicity, but overall balance and flexibility.
  • Small design details I like in Go.
  • What are named types?
  • Writing qualified Go benchmarks is not easy. (2). (3).
  • Channel in Go is a bonus feature, expect channels to solve all problems is a mistake.
• Some summaries:
  • Why can't Go programs run as fast as C programs?
  • Go syntax and semantic change history.
  • The perceivable optimizations made by the standard Go compiler (gc).
  • A summary of panic and crash cases.
  • Unspecified behaviors in Go.
• Immutable/read-only values related:
  • Lacking support for immutable values is a potential security threat for Go programs.
  • The benefits of supporting immutable and read only values.
  • A proposal to avoid duplicating underlying bytes when using strings as read only []byte arguments.
  • An immutable value proposal to let Go support final exported values.
  • A proposal to support read-only and practical immutable values in Go.
  • Go immutable value proposal list.
• More facts and details:
  • About memory ordering guarantees made by atomic operations in Go.
  • The Go standard packages are not totally standard.
  • Go specification makes very few address alignment guarantees.
  • Explain semicolon insertion rules with a small example.
  • A small detail about using value methods as function values.
• Others
  • CGO Environment Setup.
  • How to specify the minimum Go toolchain version required by a package?