Closed github-actions[bot] closed 1 year ago
This seems relevant to your interests, @bcheidemann. I'm inclined to just remove wee_alloc
entirely and rely on the default allocator, unless you've got an alternate plan.
@mpalmer ouch! I didn't realise it was un-maintained 😬 The wasm-pack
docs make reference to it so I assumed it would be ok. It's not really needed anyway so I can raise a PR to remove it.
@bcheidemann could you maybe open an issue on wasm-pack to indicate that wee_alloc should be removed from the docs so that others don't fall into the same trap? You know best where you found it mentioned there!
@corneliusroemer Thanks for reminding me :)
wee_alloc
0.4.5
Two of the maintainers have indicated that the crate may not be maintained.
The crate has open issues including memory leaks and may not be suitable for production use.
It may be best to switch to the default Rust standard allocator on wasm32 targets.
Last release seems to have been three years ago.
Possible Alternative(s)
The below list has not been vetted in any way and may or may not contain alternatives;
Honorable Mention(s)
The below may serve to educate on potential future alternatives:
See advisory page for additional details.