---
title: "Eduardo Bonzi da Conceição (@eduardobonzi) | Hashnode"
description: "Backend Developer. Read the latest articles by Eduardo Bonzi da Conceição on Hashnode."
url: "https://hashnode.com/@eduardobonzi"
---

@eduardobonzi

# Eduardo Bonzi da Conceição

@eduardobonzi · Rio de Janeiro, Brazil · Joined May 2021

Backend Developer

## Comments

[Nithin Thomas Exactly, since you're not using a mutex, you'll run into race conditions if you modify newData somewhere else in your code while one of your goroutines is also modifying it.](https://hashnode.com/posts/sharing-memory-by-communicating-in-golang/603e7f2bff443a0a4499e1b0/comment/60917b858c38d5300e68a73b#reply-60933880a7a3827bb64cd158)

Reply · Article · May 6, 2021 · [Sharing Memory by Communicating in Golang](https://hashnode.com/posts/sharing-memory-by-communicating-in-golang/603e7f2bff443a0a4499e1b0)

[I know this is a simple example but channels don't guarantee exclusive access, if you modify newData (it being a pointer) anywhere else in your code you'll probably run into a race condition. (Also there a few typos in your code, like the name of the channel in main and d.list which should be d.numbers).](https://hashnode.com/posts/sharing-memory-by-communicating-in-golang/603e7f2bff443a0a4499e1b0/comment/60917b858c38d5300e68a73b)

Comment · Article · May 4, 2021 · [Sharing Memory by Communicating in Golang](https://hashnode.com/posts/sharing-memory-by-communicating-in-golang/603e7f2bff443a0a4499e1b0)