diff --git a/.cache/plugin/social/edc66f33793b595cb892872d9d5fb7a4.png b/.cache/plugin/social/edc66f33793b595cb892872d9d5fb7a4.png new file mode 100644 index 0000000..89c5685 Binary files /dev/null and b/.cache/plugin/social/edc66f33793b595cb892872d9d5fb7a4.png differ diff --git a/docs/community.md b/docs/community.md new file mode 100644 index 0000000..2f8cf77 --- /dev/null +++ b/docs/community.md @@ -0,0 +1,15 @@ +--- +hide: +- toc +- navigation +--- + +# Community + +Thanks to all the contributors: + + + Description of the image + + +If you want to get involved, we're looking for volunteers to summarize the remaining mistakes ([GitHub issue #43](https://github.com/teivah/100-go-mistakes/issues/43)) πŸ™ diff --git a/docs/index.md b/docs/index.md index f3888a8..d2d7627 100644 --- a/docs/index.md +++ b/docs/index.md @@ -2135,11 +2135,3 @@ Read the full section [here](98-profiling-execution-tracing.md). ???+ info "TL;DR" To help avoid CPU throttling when deployed in Docker and Kubernetes, keep in mind that Go isn’t CFS-aware. - -## Community - -Thanks to all the contributors: - - - Description of the image - diff --git a/mkdocs.yml b/mkdocs.yml index 9c609c5..b885988 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -61,11 +61,11 @@ extra: extra_css: - stylesheets/extra.css nav: - - πŸ“– Book: + - Book: - book.md - chapter-1.md - external.md - - πŸ’‘οΈ Go Mistakes: + - Go Mistakes: - index.md - Full Sections: - 9-generics.md @@ -74,6 +74,7 @@ nav: - 56-concurrency-faster.md - 89-benchmarks.md - 98-profiling-execution-tracing.md + - community.md markdown_extensions: - admonition - pymdownx.details diff --git a/site/20-slice/index.html b/site/20-slice/index.html index 003a152..9443ac1 100644 --- a/site/20-slice/index.html +++ b/site/20-slice/index.html @@ -301,7 +301,7 @@ - πŸ“– Book + Book @@ -321,7 +321,7 @@ - πŸ’‘οΈ Go Mistakes + Go Mistakes @@ -329,6 +329,23 @@ + + + + +
  • + + + + + + Community + + +
  • + + + @@ -409,7 +426,7 @@ - πŸ“– Book + Book @@ -419,7 +436,7 @@ @@ -409,7 +426,7 @@ - πŸ“– Book + Book @@ -419,7 +436,7 @@ @@ -359,7 +376,7 @@ - πŸ“– Book + Book @@ -369,7 +386,7 @@ @@ -409,7 +426,7 @@ - πŸ“– Book + Book @@ -419,7 +436,7 @@ @@ -409,7 +426,7 @@ - πŸ“– Book + Book @@ -419,7 +436,7 @@ @@ -409,7 +426,7 @@ - πŸ“– Book + Book @@ -419,7 +436,7 @@ @@ -407,7 +426,7 @@ - πŸ“– Book + Book @@ -417,7 +436,7 @@ @@ -410,7 +427,7 @@ - πŸ“– Book + Book @@ -420,7 +437,7 @@ @@ -412,7 +429,7 @@ - πŸ“– Book + Book @@ -422,7 +439,7 @@ @@ -410,7 +427,7 @@ - πŸ“– Book + Book @@ -420,7 +437,7 @@ @@ -407,7 +424,7 @@ - πŸ“– Book + Book @@ -417,7 +434,7 @@ @@ -3144,15 +3172,6 @@ - - -
  • - - - Community - - -
  • @@ -3421,14 +3440,12 @@ Granularity is another essential thing to consider. We should avoid having dozen
  • https://golang.org/cmd/vetβ€”A standard Go analyzer
  • https://github.com/kisielk/errcheckβ€”An error checker
  • https://github.com/fzipp/gocycloβ€”A cyclomatic complexity analyzer
  • -
  • https://github.com/jgautheron/goconstβ€”A repeated string constants analyzer -* -Besides linters, we should also use code formatters to fix code style. Here is a list of some code formatters for you to try:
  • -
  • https://golang.org/cmd/gofmtβ€”A standard Go code formatter
  • -
  • https://godoc.org/golang.org/x/tools/cmd/goimportsβ€”A standard Go imports formatter -* -Meanwhile, we should also look at golangci-lint (https://github.com/golangci/golangci-lint). It’s a linting tool that provides a facade on top of many useful linters and formatters. Also, it allows running the linters in parallel to improve analysis speed, which is quite handy.
  • +
  • https://github.com/jgautheron/goconstβ€”A repeated string constants analyzer
  • +

    Besides linters, we should also use code formatters to fix code style. Here is a list of some code formatters for you to try: +* https://golang.org/cmd/gofmtβ€”A standard Go code formatter +* https://godoc.org/golang.org/x/tools/cmd/goimportsβ€”A standard Go imports formatter

    +

    Meanwhile, we should also look at golangci-lint (https://github.com/golangci/golangci-lint). It’s a linting tool that provides a facade on top of many useful linters and formatters. Also, it allows running the linters in parallel to improve analysis speed, which is quite handy.

    Linters and formatters are a powerful way to improve the quality and consistency of our codebase. Let’s take the time to understand which one we should use and make sure we automate their execution (such as a CI or Git precommit hook).

    Data Types

    Creating confusion with octal literals (#17)

    @@ -4781,11 +4798,6 @@ the use case. However, we should see the two options as complementary.

    TL;DR

    To help avoid CPU throttling when deployed in Docker and Kubernetes, keep in mind that Go isn’t CFS-aware.

    -

    Community

    -

    Thanks to all the contributors:

    -

    - Description of the image -

    diff --git a/site/ja/index.html b/site/ja/index.html index 4335f0d..da6e16b 100644 --- a/site/ja/index.html +++ b/site/ja/index.html @@ -297,7 +297,7 @@ - πŸ“– Book + Book @@ -315,7 +315,7 @@ - πŸ’‘οΈ Go Mistakes + Go Mistakes @@ -323,6 +323,23 @@ + + + + +
  • + + + + + + Community + + +
  • + + + @@ -401,7 +418,7 @@ - πŸ“– Book + Book @@ -411,7 +428,7 @@ @@ -403,7 +420,7 @@ - πŸ“– Book + Book @@ -413,7 +430,7 @@ @@ -401,7 +418,7 @@ - πŸ“– Book + Book @@ -411,7 +428,7 @@