Zig Version
0.16.0
Steps to Reproduce, Observed Behavior, and Expected Behavior
MemoryPool runs ptr.* = undefined; both on create and destroy, and there is no way to opt-out of it. This is a big issue, when one wants to use memory pool as fast access to larger storage, as it can easily become performance bottleneck (again, without a way to opt-out of it).
### Zig Version
0.16.0
### Steps to Reproduce, Observed Behavior, and Expected Behavior
MemoryPool runs `ptr.* = undefined;` both on create and destroy, and there is no way to opt-out of it. This is a big issue, when one wants to use memory pool as fast access to larger storage, as it can easily become performance bottleneck (again, without a way to opt-out of it).
Also see https://ziggit.dev/t/releasesafe-slower-than-debug-and-performance-degrading-with-larger-buffers/15916/11