This repo needs to be archived and marked as deprecated #109

Activity

1. spencerbart

   added

   bugSomething isn't workingSomething isn't working

   on Feb 28, 2023
2. spencerbart

   changed the title [-]This repo needs to be archived and marked as depreciated[/-] [+]This repo needs to be archived and marked as deprecated[/+] on Feb 28, 2023
3. erwanvivien commented on Mar 1, 2023

   

   erwanvivien

   on Mar 1, 2023

   More actions

   Agreed
4. jack-mil commented on Apr 23, 2023

   

   jack-mil

   on Apr 23, 2023

   More actions

   Yes I am beginning to see that a lot of the the Rust wasm ecosystem is outdated and not working well in 2023.
   Specifically the tutorials and book provided from https://rustwasm.github.io/ has not been updated for years and does not work out of the box.
   What is the modern tooling for wasm with rust, besides wasm-pack and friends?

   😕React with 😕2Reacted by Sammy Harris and Jarrod Davis
5. FlogramMatt commented on May 22, 2023

   

   FlogramMatt

   on May 22, 2023

   More actions

   Major security issue? You mean the memory leak? You do realize it's impossible to free wasm memory.. I would say this is a wasm issue not this library. I bet the standard allocator has the same issue..
6. erwanvivien commented on May 23, 2023

   

   erwanvivien

   on May 23, 2023

   Last edited by erwanvivien

   More actions

   #106 (comment)

   Making two large allocations, then dropping them in the order they were allocated leaks memory in wee_alloc, but not in default allocator.

   Hello @FlogramMatt. I believe not, this issue says otherwise
7. benma

   added a commit that references this issue on Aug 3, 2023

   remove unmaintained weealloc

   ...

   e71e4c3