|
You are here |
www.foonathan.net | ||
| | | | |
blog.molecular-matters.com
|
|
| | | | | As promised last time, today we will see how pool allocators can help with allocating/freeing allocations of a certain size, in any order, in O(1) time. Use cases Pool allocators are extremely helpful for allocating/freeing objects of a certain size which often have to be created/destroyed dynamically, such as weapon bullets, entity instances, rigid bodies,... | |
| | | | |
coredumped.dev
|
|
| | | | | Back in 2019, Nick Fitzgerald published always bump downwards, an article making the case that for bump allocators, bumping "down" (towards lower addresses) is better than bumping up. The biggest reasons for this are bumping up requires 3 branches vs 2 for bumping down and rounding down requires fewer instructions than rounding up. This became the method used for the popular bumpalo crate. In this post, I want to go back and revisit that analysis. | |
| | | | |
thenumb.at
|
|
| | | | | ||
| | | | |
borretti.me
|
|
| | | Reflections on using Rust professionally for two years. | ||