Folly - The Faceboook open source library

Post by chasingtheflow » Mon, Jun 04, 2012, 2:40 AM UTC

dreiss wrote: post #22

joe_the_user wrote: post #10

Earlier quoted context omitted.

Hmm, I recently created a private memory allocator so the discussion on the page is somewhat interesting... Only a tiny minority of objects are genuinely non-relocatable: Hmm, I'm not exactly what is meant here. Moving a block of memory from here to there in the most general case will leave your pointers dangling and crash you in no short order. Things that pointed to the data you moved just don't any more. If you ar…

If your object is in a vector, it's already possible for the vector to move the object without updating any pointers to it. The only question is whether it is safe for the vector to move the object with memmove instead of invoking a copy/move constructor, essentially skipping the step of telling the object that it is being moved. This will only fail if the object contains pointers to its own sub-objects (or the move…

Post by tudorb » Mon, Jun 04, 2012, 2:43 PM UTC

alainbryden wrote: post #7

This is a conspiracy theory, but what if there are bugs in it that they can't find and so they're open sourcing it in the hope that someone else will fix it.