book
wee_alloc
| book | wee_alloc | |
|---|---|---|
| 4 | 7 | |
| 466 | 632 | |
| 0.0% | 0.0% | |
| 4.5 | 0.0 | |
| 4 months ago | about 1 year ago | |
| Rust | Rust | |
| Creative Commons Attribution 4.0 | Mozilla Public License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
book
-
I'm wanting to write my first compiler, but getting a little bit mixed up in general.
Kind of an interpreter but it does compile to bytecode and is written in rust https://github.com/rust-hosted-langs/book I thought it was a great tutorial, both for learning rust, and about compilers
-
Best resources for a rust interpreter?
Then go to: - rust-hosted-langs/book: Writing Interpreters in Rust: a Guide or https://craftinginterpreters.com/
-
I'm building a dynamic language in Rust
https://github.com/rust-hosted-langs/book is a work in progress
wee_alloc
-
Rust + WASM + Typescript [+ React]
As a note, you might find some references to use wee_alloc, but it has been unmaintained for some time and shouldn't be used. I'm using the default allocator with the wasm32-wasi target and it works fine, but I don't know if that works with wasm32-unknown-unknown too; if not there's lol_alloc.
-
Junior Dev here -- How are we setting up Rust, WASM, and webpack?
Note that the wasm-pack tutorial recommends using the wee_alloc crate. This crate is unmaintained and leaks memory, so it should be avoided. Remove this crate, the default allocator works just fine in WebAssembly.
-
Don't use wee_alloc in production code targeting WebAssembly.
It leaks memory: https://github.com/rustwasm/wee_alloc/issues/106
-
Need advice on a project involving Webassembly+ web_sys + webgl
Last thing that comes to mind is switching the allocator to wee_alloc. I use it most of the time for wasm projects and it doesn't make too much of a difference in binary size but that always depends on the project and usually saves at least a few kB.
-
Developing a cross-platform game for browser, Ios, and Android using rust?
For example, check out wee_alloc.
-
Rust on the front-end
wee_alloc, an allocator optimized for small code size.
-
#![no_std] with WASI is more complicated than I thought it would be
Ok. Now I need to add in a global allocator. I use wee_alloc since I know it works pretty well with WASM: Cargo.toml
What are some alternatives?
sphinx-lang - An intepreter for a simple dynamic language written in Rust
wasm-bindgen - Facilitating high-level interactions between Wasm modules and JavaScript
simple-chunk-allocator - A simple allocator written in Rust that manages memory in fixed-size chunks.
wasi-libc - WASI libc implementation for WebAssembly
cactusref - 🌵 Cycle-Aware Reference Counting in Rust
cargo-wasi - A lightweight Cargo subcommand to build Rust code for the `wasm32-wasi` target
luxya - Programming language with a tree-walking interpreter written in Rust©™.
create-wasm-app - npm init template for consuming rustwasm pkgs
proc - Procedural Intel x86_64 compiler from scratch, inspired by Fortran, Pascal and Assembly.
compiler-builtins - Porting `compiler-rt` intrinsics to Rust
mmtk-core - Memory Management ToolKit
wasm-pack - 📦✨ your favorite rust -> wasm workflow tool!