mirror of
https://github.com/teivah/100-go-mistakes.git
synced 2026-06-21 00:47:11 +08:00
Minor.
This commit is contained in:
parent
1af0884ef4
commit
467866b38f
4 changed files with 5 additions and 5 deletions
|
|
@ -591,7 +591,7 @@ This code updates the last index to 10. However, if we run this code, it does no
|
|||
|
||||
???+ warning
|
||||
|
||||
This mistake isn't relevant anymore from Go 1.22 ([source](https://go.dev/blog/loopvar-preview)).
|
||||
This mistake isn't relevant anymore from Go 1.22 ([details](https://go.dev/blog/loopvar-preview)).
|
||||
|
||||
### Making wrong assumptions during map iterations (ordering and map insert during iteration) (#33)
|
||||
|
||||
|
|
@ -1510,7 +1510,7 @@ In summary, let’s be mindful that a goroutine is a resource like any other tha
|
|||
|
||||
???+ warning
|
||||
|
||||
This mistake isn't relevant anymore from Go 1.22 ([source](https://go.dev/blog/loopvar-preview)).
|
||||
This mistake isn't relevant anymore from Go 1.22 ([details](https://go.dev/blog/loopvar-preview)).
|
||||
|
||||
### Expecting a deterministic behavior using select and channels (#64)
|
||||
|
||||
|
|
|
|||
|
|
@ -3668,7 +3668,7 @@ One additional note: we must remember that the standard library has some existin
|
|||
<h3 id="ignoring-the-impacts-of-using-pointer-elements-in-range-loops-32">Ignoring the impacts of using pointer elements in <code>range</code> loops (#32)</h3>
|
||||
<details class="warning" open="open">
|
||||
<summary>Warning</summary>
|
||||
<p>This mistake isn't relevant anymore from Go 1.22 (<a href="https://go.dev/blog/loopvar-preview">source</a>).</p>
|
||||
<p>This mistake isn't relevant anymore from Go 1.22 (<a href="https://go.dev/blog/loopvar-preview">details</a>).</p>
|
||||
</details>
|
||||
<h3 id="making-wrong-assumptions-during-map-iterations-ordering-and-map-insert-during-iteration-33">Making wrong assumptions during map iterations (ordering and map insert during iteration) (#33)</h3>
|
||||
<details class="info" open="open">
|
||||
|
|
@ -4359,7 +4359,7 @@ the use case. However, we should see the two options as complementary. </p>
|
|||
<h3 id="not-being-careful-with-goroutines-and-loop-variables-63">Not being careful with goroutines and loop variables (#63)</h3>
|
||||
<details class="warning" open="open">
|
||||
<summary>Warning</summary>
|
||||
<p>This mistake isn't relevant anymore from Go 1.22 (<a href="https://go.dev/blog/loopvar-preview">source</a>).</p>
|
||||
<p>This mistake isn't relevant anymore from Go 1.22 (<a href="https://go.dev/blog/loopvar-preview">details</a>).</p>
|
||||
</details>
|
||||
<h3 id="expecting-a-deterministic-behavior-using-select-and-channels-64">Expecting a deterministic behavior using select and channels (#64)</h3>
|
||||
<details class="info" open="open">
|
||||
|
|
|
|||
File diff suppressed because one or more lines are too long
Binary file not shown.
Loading…
Reference in a new issue