Rust: Dropping heavy things in another thread can make your code 10000x faster

Re:Rust: Dropping heavy things in another thread can make yo... by MaxBarraclough on Saturday May 30, 2020 @04:19PM (#23364302)

A pool can invoke destructors when it is cleared. Might take a bit of overhead (if the pool is to support arbitrary classes), but you could retain the fast pointer-bump allocation.

[ Parent | on HN ]

Re:Rust: Dropping heavy things in another thread can make yo... by ShroudedNight on Saturday May 30, 2020 @07:59PM (#23365959)

Not Rust, C++, but in case anybody wants an example: https://github.com/eclipse/omr/commit/fd99ca42fdbed76cc00e68...

TR::Region is the slab allocator used by the JIT in OpenJ9/OMR. The linked commit adds functionality for calling destructors of arbitrary types allocated in the Region.

[ Parent | on HN ]

Re:Rust: Dropping heavy things in another thread can make yo... by MaxBarraclough on Sunday May 31, 2020 @02:18PM (#23371420)

Interesting, thanks. Seems to require use of a common base class though, i.e. to use a class with this pool, you have to inherit from Destructable, or else create a subclass that does. Seems ugly. Perhaps that's the only way it can be done in C++ though.

[ Parent | on HN ]

Re:Rust: Dropping heavy things in another thread can make yo... by projektfu on Monday June 01, 2020 @03:45PM (#23382873)

It does create an object with that base class for the allocator but returns an object of the type you want from the allocator, using a template (Region::Instance<T>). So the API user only sees the types it's interested in.

[ Parent | on HN ]