top | item 36451530

(no title)

dxhdr | 2 years ago

It's essentially a "user-space" memory allocator with it's own use-after-free and double-free checks, apparently because the language implementation isn't adequate. If anything it just reinforces the articles point that "borrow checking is incompatible with some useful patterns and optimizations."

discuss

order

junon|2 years ago

Eh? This is a wild take. How do you draw the conclusion the default implementation is inadequate?

dymk|2 years ago

Because something like slotmap has to use `unsafe` to get around the inadequacies of the borrow checker...