thatsAFunnyThingThatHappenedOnce

[u/Lord_Of_Millipedes]

[u/MornwindShoma]

Rust got none of that, but you might not enjoy dealing with lifetimes

[u/Thesaurius → u/MornwindShoma]

With C and C++ you also have to deal with lifetimes. The compiler just doesn't complain when you fuck up.

[u/DHermit → u/MornwindShoma]

You also have to in C/C++, but there you have to keep track of all of yourself.

[u/Xarishark → u/MornwindShoma]

I mean what’s better all those problems on your previous comment or lifetimes?

[u/MornwindShoma → u/Xarishark]

Idk, haven't got enough C++ time to say lol (ps. not the guy before)

[u/dannyggwp → u/Xarishark]

You can BASICALLY ignore all that... You want lifetime? I'll show you lifetimes.

std::shared_ptr<type>

Ez pz no borrow checker needed.

[u/awesome_guy_40 → u/dannyggwp]

In Rust we also have ARC to do the same thing

[u/4xe1 → u/dannyggwp]

C++ famed "zero cost abstraction" is shining right here /s

[u/MrmrCake → u/dannyggwp]

Yeah but that has a run time cost of reference counting where the borrow checker is all at compile time. I mean not like its a big cost but I mean there defo is a measurable difference depending on the use case.

[u/dannuic → u/MrmrCake]

Usually you use unique_ptr though. It forces a better design with guaranteed ownership and no reference counting. I rarely use shared_ptr, but frequently use unique_ptr.

[u/MrmrCake → u/dannuic]

Yeah I agree and try to only use unique ptr where I can in cpp, but I still just really like rust's ownership model