From c80332db817c51b6ef91e0c0f25360d421d4dc94 Mon Sep 17 00:00:00 2001 From: ErdemOzgen Date: Sun, 7 Jan 2024 14:19:29 +0300 Subject: [PATCH] Update link to full section on concurrency --- content/ProgramingLang/golang/Go Common Mistakes.md | 2 +- content/ProgramingLang/golang/Learn Go with Tests.md | 0 2 files changed, 1 insertion(+), 1 deletion(-) create mode 100644 content/ProgramingLang/golang/Learn Go with Tests.md diff --git a/content/ProgramingLang/golang/Go Common Mistakes.md b/content/ProgramingLang/golang/Go Common Mistakes.md index beae2130a..c37f96287 100644 --- a/content/ProgramingLang/golang/Go Common Mistakes.md +++ b/content/ProgramingLang/golang/Go Common Mistakes.md @@ -1687,7 +1687,7 @@ In summary, concurrency provides a structure to solve a problem with parts that To be a proficient developer, you must acknowledge that concurrency isn’t always faster. Solutions involving parallelization of minimal workloads may not necessarily be faster than a sequential implementation. Benchmarking sequential versus concurrent solutions should be the way to validate assumptions. -Read the full section [here](56-concurrency-faster.md). +Read the full section [here](https://100go.co/56-concurrency-faster/). [Source code :simple-github:](https://github.com/teivah/100-go-mistakes/tree/master/src/08-concurrency-foundations/56-faster/) diff --git a/content/ProgramingLang/golang/Learn Go with Tests.md b/content/ProgramingLang/golang/Learn Go with Tests.md new file mode 100644 index 000000000..e69de29bb