PlexSheep comments on Learning to program in rust

Programmer Humor

34,003 readers

8,254 active

3 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

Keep content in english
No advertisements
Posts must be related to programming or programmer topics
- If the mod doesn't find it funny, you're banned. Ha-ha!... For real: do not use the community for "statements". There are other places for such content. Keep it chill and funny.

founded 3 years ago

moderators

[–] PlexSheep@infosec.pub 1 point 1 year ago (4 children)

You mean mutex? Arc allows synchronous read only access by multiple threads, so it's not a performance bottleneck. Locking a mutex would be one.

permalink

fedilink

source

parent

hideshow 4 child comments

[–] tatterdemalion@programming.dev 5 points 1 year ago (2 children)

Arc is not free, and the extra atomic operations + heap allocations can become a bottleneck.

permalink

fedilink

source

parent

hideshow 2 child comments

[–] PlexSheep@infosec.pub 1 point 1 year ago (1 child)

Oh, I did not know that. Well, it makes sense that it has a heap allocation, as it becomes more or less global. Though not sure why the atomic operations are needed when the value inside is immutable.

permalink

fedilink

source

parent

hideshow 1 child comment

[–] Miaou@jlai.lu 1 point 1 year ago

How can you otherwise keep track of an object's lifetime if copies are made concurrently?

permalink

fedilink

source

parent

[–] mholiv@lemmy.world 3 points 1 year ago* (last edited 1 year ago)

I mean it could be Mutex, or Rwlock or anything atomic. It’s just when I have to put stuff into an Arc<> to pass around I know trouble is coming.

permalink

fedilink

source

parent