refactor(allocator/pool): share AllocatorGuard between pool impls#13621
Conversation
CodSpeed Instrumentation Performance ReportMerging #13621 will not alter performanceComparing Summary
Footnotes |
02481be to
aed935a
Compare
7a28218 to
fbeb154
Compare
Merge activity
|
…13621) Refactor. We have 2 versions of `AllocatorPool` (standard and fixed-size). Aim is to combine them into one. This is a step along that way. Previously both versions of `AllocatorPool` had very similar `AllocatorGuard` implementations. Replace them with a single `AllocatorGuard` implementation, which both versions share.
aed935a to
0dde7f0
Compare
fbeb154 to
99dd1a7
Compare
camc314
left a comment
There was a problem hiding this comment.
// SAFETY:
FixedSizeAllocatoris just a wrapper aroundManuallyDrop<Allocator>,
are there any const assertions we can add to prevent this breaking
There is a ton of hackery around allocators at the moment, and this isn't even the worst of it. Ultimately, I think we need to replace |

Refactor.
We have 2 versions of
AllocatorPool(standard and fixed-size). Aim is to combine them into one. This is a step along that way.Previously both versions of
AllocatorPoolhad very similarAllocatorGuardimplementations. Replace them with a singleAllocatorGuardimplementation, which both versions share.