proc-macro-workshop
wasm-bindgen
proc-macro-workshop | wasm-bindgen | |
---|---|---|
26 | 44 | |
3,836 | 7,284 | |
- | 1.2% | |
4.3 | 9.1 | |
26 days ago | 8 days ago | |
Rust | Rust | |
Apache License 2.0 | Apache 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.
proc-macro-workshop
-
Why does the core not provide a "New" derive attribute?
Tangentially, the proc macro workshop walks through building a derive macro implementing a builder pattern. From experience, I can tell I couldn't ever write proc macros just by reading the manual, going through it is really helpful https://github.com/dtolnay/proc-macro-workshop/blob/master/README.md
-
Help on spans for proc macros
I am working on the proc macro workshop and am a little stuck on the builder portion of the workshop. Step 08-unrecognized-attributes wants you to handle the car where the field modifier has a misspelled portion (eac instead of each)
-
Practical Procedural Macros in Rust
I would very much second the suggestion to do David Tolnay’s Proc Macro Workshop if you want to start understanding how to write them. I’d been writing Rust for years but always kind of avoided proc macros.
When I had a need for them, I went through only the first section of the workshop and everything clicked. You can just do the derive macro section and all the strange and scary-looking macro syntax will make sense. I realized that there is only a bit of extra syntax but it’s used very often so it can seem a little overwhelming when reading macro code.
https://github.com/dtolnay/proc-macro-workshop
- Rust fact vs. fiction: 5 Insights from Google's Rust journey in 2022
-
A walkthough on how to write derive procedural macros
Another good one imo is the proc-macro-workshop.
-
Transitioning to Rust as a company
Don't be afraid of proc macros and derive macros, they rule. Study the basic examples. Crates like darling and resources like David Tolnay's workshop will help. Write derives for your simpler traits and impress your colleagues.
-
What are your experiences with hack-and-learn events?
Regarding 4, I think that macros are an interesting intermediate/advanced topic. I personally loved the material from https://github.com/dtolnay/proc-macro-workshop
-
Procedural Macros are really hard to understand
It took me a while to get anything done. My mistake : I came accross the procedural macros workshop several times, and every time I dismissed it, thinking - meh I'll just hack together exactly what I need and move on. Then finally I figured there is no way around it. The builder exercise sounds boring but it covers the topic pretty well. And then I went on to the debug one and from there was able to build the proc macro I wanted.
-
MacroKata is really good!
Hey! While researching, I found this: https://github.com/dtolnay/proc-macro-workshop
-
Anything C can do Rust can do Better
Rust Latam: procedural macros workshop - David Tolnay
wasm-bindgen
-
If the native speed DOM/Web API for Rust becomes a reality, would you be willing to build your web apps with Rust and HTML/CSS?
Another strange issue could be seen in the strict class heritage organized definition of the DOM, which can not be handled very well by rust because of a still unsolved bindgen issue (#210).
-
Rust + WASM + Typescript [+ React]
For a much simpler but less flexible approach there's wasm-pack for creating JS packages from Rust, and wasm-bindgen for easy interop. Both have very good documentation.
-
We Just Released our Rust WebTransport Teleconferencing System - Here are Some Lessons Learned
We encountered quite a few hurdles on our journey. For one, we had to build our own yew-webtransport and yew-websocket integration from scratch by adding WebTransport definitions to wasm-bindgen (pull request link). We also had to add WebTransport support to the h3 crate (pull request link). co-created by @ten3roberts
-
Looking to create a backend service for a website in Rust and I’m wondering on how to best do it
Go with your WebAssembly module idea. Since it sounds like your chess engine does not draw a UI, it shouldn't be too difficult. wasm-bindgen will be your best friend.
-
Ask HN: How can a BE/infra developer handle the FE side of personal projects?
I've never tried it, but apparently some bindings exist, e.g. https://github.com/rustwasm/wasm-bindgen
So you can either try manipulating the DOM w/ some bindings or draw to canvas.
-
I'm trying to compile my rust code to wasm but wasm_bindgen says the trait bound `(Vec<i32>, Vec<i32>): IntoWasmAbi` is not satisfied.
Google also brings up this GitHub issue.
-
Deno Fresh WASM: Code Modules in Rust
If you want to learn more on wasm-pack, there is a wasm-pack book as well as some fairly detailed wasm-bindgen docs. There are a few resources for learning Rust itself in the December newsletter. Finally, please get in touch if you would like to see more content on Deno and Fresh. I hope you found the content useful and am keen to hear about possible improvements.
-
Swift Achieved Dynamic Linking Where Rust Couldn't
Love the article.
In my mind I see the problem of dynamic linking in rust to have a bunch of overlap with the "I want this rust library to be exposed in my higher level GC'd language with minimal safety/handwritten bindings" problem.
My hunch is that the lack of expressiveness of the C ABI is holding back both. the thing I'd love to see some sort of "higher level than the C ABI" come out. And something like `wasm-bindgen`[0] to exist for more languages.
Here's a link to the rust "interopable_api" proposal! I don't understand all the implications, but it seems to be in the right direction https://github.com/rust-lang/rust/pull/105586
[0]https://rustwasm.github.io/docs/wasm-bindgen/
-
The Next Browser Language
Rust has https://github.com/rustwasm/wasm-bindgen and https://crates.io/crates/sledgehammer, the latter of which batches together JS calls to reduce the FFI cost. https://dioxuslabs.com/ uses these to great effect.
-
1Password releases Typeshare, the "ultimate tool for synchronizing your type definitions between Rust and other languages for seamless FFI"
This seems like it could be super useful for integrating with wasm-bindgen and TypeScript. Last I checked, the types generated by wasm-bindgen left a lot to be desired (no disrespect intended, wasm-bindgen is an awesome project). A few years ago, I contributed the skip_typescript attribute to wasm_bindgen that allowed you to override the type generation by hand-writing your own types (using a custom typescript section), but I wonder if this could simply generate higher quality types without the manual intervention.
What are some alternatives?
sccache - Sccache is a ccache-like tool. It is used as a compiler wrapper and avoids compilation when possible. Sccache has the capability to utilize caching in remote storage environments, including various cloud storage options, or alternatively, in local storage.
wasm-pack - 📦✨ your favorite rust -> wasm workflow tool!
cargo-expand - Subcommand to show result of macro expansion
react-three-fiber - 🇨🇭 A React renderer for Three.js
rust-learnings - Collection of Rust learnings through implementation
wasmer - 🚀 The leading Wasm Runtime supporting WASIX, WASI and Emscripten
style - css for rust
wasmtime - A fast and secure runtime for WebAssembly
quote - Rust quasi-quoting
trunk - Build, bundle & ship your Rust WASM application to the web.
style - Style Dart Backend Framework
wasi-libc - WASI libc implementation for WebAssembly