539
top 35 comments
sorted by: hot top controversial new old
[-] Guilvareux@feddit.uk 24 points 1 year ago
[-] meisme@lemmy.world 4 points 1 year ago
[-] philm@programming.dev 4 points 1 year ago
[-] tatterdemalion@programming.dev 1 points 1 year ago* (last edited 1 year ago)

Are you copying a Result or Option?

[-] philm@programming.dev 2 points 1 year ago

I don't understand...? I think I never explicitly run a method/function that is called copy (there isn't at least not for the trait Copy)

[-] tatterdemalion@programming.dev 2 points 1 year ago

Lol yea I think the .copy() comment was a little gaslighting or something.

[-] darcy@sh.itjust.works 2 points 1 year ago

no its not youre crazy

[-] pulaskiwasright@lemmy.ml 22 points 1 year ago* (last edited 1 year ago)

I thought it was randomly adding Send and Sync traits to function signatures until rustc is happy.

[-] theory@feddit.uk 2 points 1 year ago
[-] charolastra@programming.dev 4 points 1 year ago

Randomly wrapping things in Arc::new()

[-] danwardvs@sh.itjust.works 21 points 1 year ago

This was me in courses that used C. Keep adding and removing * and & until the IDE was happy and it usually worked.

[-] philm@programming.dev 8 points 1 year ago

Ah the good old times with C, when things were much more simple (but unsafe...)

[-] rikudou@lemmings.world 3 points 1 year ago

(void*) flashbacks intensify.

[-] philm@programming.dev 3 points 1 year ago

The "best" way to program dynamically typed...

[-] mvee@lemmy.ml 18 points 1 year ago

I'm gonna have to borrow this book

[-] HeavyRust@lemm.ee 6 points 1 year ago

Me too. I also want to make some changes to it at the same time.

[-] mvee@lemmy.ml 4 points 1 year ago

Better apply for a mutable library card now before someone else does

[-] SubArcticTundra@lemmy.ml 16 points 1 year ago

Hahaha yes tfw Rust forces you to put your shit in a Rc<Cell<Option<>>>

[-] nothacking@discuss.tchncs.de 6 points 1 year ago

New your program deadlocks instead of crashing, peak safety.

[-] tatterdemalion@programming.dev 9 points 1 year ago

EVERYBODY STOP. Nobody make a move or the memory dies. We have a Mexican Memory Standoff.

[-] Blackthorn@programming.dev 13 points 1 year ago

Follow up of: "Mmm... should I put lifecycle annotation in these 10 structs or just use and Rc and call it a day?". Rc and Box FTW.

[-] raubarno@lemmy.ml 12 points 1 year ago

So... now the rustc borrow checker is the new video game boss that is nearly impossible to beat for newcomers, right?

[-] nothacking@discuss.tchncs.de 4 points 1 year ago

Same for C, & yields a pointer to a value, and * allows you to access the data. (For rust people, a pointer is like a reference with looser type checking)

[-] aloso@programming.dev 6 points 1 year ago

We have pointers in Rust, too :) see documentation

[-] nothacking@discuss.tchncs.de 3 points 1 year ago

I doubt many people have ever use that or any of the other low level memory API. The main appeal of rust is not having to do that.

[-] aloso@programming.dev 1 points 1 year ago

Sure, but raw pointers and unsafe Rust are still covered in the official learning material, so I assume that most Rust devs know about raw pointers.

[-] skomposzczet@lemm.ee 4 points 1 year ago* (last edited 1 year ago)

I think that's the only thing I dislike about rust. Not having to use * to dereference but later having to use is tad confusing. I know it's still clever solution but in this case I prefer c++'s straightforward consistency.

Using ampersand never was problematic for me.

[-] Pfosten@feddit.de 24 points 1 year ago

C++ does have the problem that references are not objects, which introduces many subtle issues. For example, you cannot use a type like std::vector<int&>, so that templated code will often have to invoke std::remove_reference<T> and so on. Rust opts for a more consistent data model, but then introduces auto-deref (and the Deref trait) to get about the same usability C++ has with references and operator->. Note that C++ will implicitly chain operator-> calls until a plain pointer is reached, whereas Rust will stop dereferencing once a type with a matching method/field is found. Having deep knowledge of both languages, I'm not convinced that C++ features "straightforward consistency" here…

[-] nautilus@lemmy.dbzer0.com 3 points 1 year ago

Replace that with golang and now we’re talking

[-] BravoVictor@programming.dev 2 points 1 year ago

Yeah, popped in the comments to say the same.

I dont know what my damage is with pointers…

[-] nautilus@lemmy.dbzer0.com 3 points 1 year ago

honestly with Go in general I’m in a perpetual cycle of being annoyed with it and then immediately being amazed when I find some little trick for efficiency - with stringer interfaces and the like

[-] preasket@lemy.lol 0 points 1 year ago
[-] Anafabula@discuss.tchncs.de 12 points 1 year ago
[-] PipedLinkBot@feddit.rocks 7 points 1 year ago

Here is an alternative Piped link(s): https://piped.video/watch?v=TGfQu0bQTKc

Piped is a privacy-respecting open-source alternative frontend to YouTube.

I'm open-source, check me out at GitHub.

[-] PipedLinkBot@feddit.rocks 2 points 1 year ago

Here is an alternative Piped link(s): https://piped.video/watch?v=co3ewqQlX-8

Piped is a privacy-respecting open-source alternative frontend to YouTube.

I'm open-source, check me out at GitHub.

load more comments
view more: next ›
this post was submitted on 15 Jul 2023
539 points (98.0% liked)

Programmer Humor

19450 readers
240 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

founded 1 year ago
MODERATORS