News for hackers. Stuff that matters.

A comment on Taming Go’s memory usage, or how we avoided rewriting our client in Rust. Parent comment

Re:Taming Go’s memory usage, or how we avoided rewriting our... by oconnor663 on Tuesday September 21, 2021 @04:02PM (#28609252)
I think before the introduction of move semantics in C++11, there were a lot of cases where you needed new and delete to get basic things working. (Moving an fstream around is a relevant example.) So the modern rule of "don't use new and delete in application code" really wasn't practical before that.
[ Parent | on HN ]
Re:Taming Go’s memory usage, or how we avoided rewriting our... by jcelerier on Tuesday September 21, 2021 @06:32PM (#28610847)
No, pretty much everything could be done with swap (like moving an fstream as you say). Sure, it's a bit more cumbersome, but it was still RAII.
[ Parent | on HN ]
Re:Taming Go’s memory usage, or how we avoided rewriting our... by nyanpasu64 on Tuesday September 21, 2021 @07:20PM (#28611240)
I suppose RAII is an old concept, but move semantics allowing RAII to transfer ownership and avoid manual new/free of non-copied resources was uncommon until C++11.
[ Parent | on HN ]