proc-macro-workshop
warp
proc-macro-workshop | warp | |
---|---|---|
26 | 66 | |
3,836 | 9,158 | |
- | - | |
4.3 | 6.4 | |
27 days ago | 30 days ago | |
Rust | Rust | |
Apache License 2.0 | MIT License |
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
warp
-
Hyper – A fast and correct HTTP implementation for Rust
I tried warp [0] and I am unimpressed so far. Pretty complex, limited documentation, buggy. The builder paradigm they used feels pretty constrained and, in my opinion, achieve the opposite of the simplicity it is supposed to bring. I was surprised it is so popular.
Maybe I need more time or a favorable comparison to another framework to appreciate it.
[0] https://github.com/seanmonstar/warp
-
How in hell can Warp be considered "super easy"?
Have you gone through the (examples)[https://github.com/seanmonstar/warp/blob/master/examples/]? There's actually a lot of explicit instructions here on how to use Warp, and all of them are very straightforward to read (e.g., (this example with route parameters and a POST'ed body)[https://github.com/seanmonstar/warp/blob/master/examples/body.rs])
-
Custom Warp error messages
There are numerous guides how to do custom error messages using the routes .recover() method (including the official one ), but it seems quite inflexible since I can't (seem to?) pass the actual error messages back to user.
-
Rendering a Rust project's file dependency tree in the terminal
$ brew install gabotechs/taps/dep-tree $ git clone https://github.com/seanmonstar/warp $ dep-tree render warp/src/lib.rs lib.rs◁─────────────┬────────────────────────────────┬──────┬┐ │ │ │ ││ ├▷filter/and.rs◁────────────────────────────┐ │ ││ ├▷│filter/map_err.rs◁───────────────────────┤ │ ││ ├▷││filter/or.rs◁───────────────────────────┤ │ ││ ├▷│││filters/mod.rs◁─────────────┬──────┬───────────────────┼┤ ├▷││││test.rs───────┘ │ │ │ │ ││ │ │││││ │ │ │ │ ││ │ │││├│▷filters/addr.rs │ │ │ │ ││ │ │││├│▷│filters/any.rs │ │ │ │ ││ │ │││├│▷││filters/body.rs │ │ │ │ ││ │ │││├│▷│││filters/compression.rs│ │ │ │ ││ │ │││├│▷││││filters/cookie.rs────┘ │ │ │ ││ │ │││├│▷│││││filters/cors.rs │ │ │ ││ │ │││├│▷││││││filters/ext.rs │ │ │ ││ │ │││├│▷│││││││filters/fs.rs │ │ │ ││ │ │││├│▷││││││││filters/header.rs │ │ │ ││ │ │││├│▷│││││││││filters/host.rs │ │ │ ││ │ │││├│▷││││││││││filters/log.rs │ │ │ ││ │ │││├│▷│││││││││││filters/method.rs │ │ │ ││ │ │││├│▷││││││││││││filters/multipart.rs│ │ │ ││ │ │││├│▷│││││││││││││filters/path.rs────┤ │ │ ││ │ │││├│▷││││││││││││││filters/query.rs │ │ │ ││ │ │││├│▷│││││││││││││││filters/reply.rs │ │ │ ││ │ │││├│▷││││││││││││││││filters/sse.rs──┘ │ │ ││ │ │││├│▷│││││││││││││││││filters/trace.rs │ │ ││ │ │││││ ││││││││││││││││││ │ │ ││ ├─────────────────────────▷filter/boxed.rs◁─┤ │ ││ ├─────────────────────────▷│filter/map.rs◁──┤ │ ││ ├─────────────────────────▷││filter/wrap.rs◁┼───────────────┼─┐ │ │││││ ││││││││││││││││││ │││ │ │ │││ ├─────────────────────────────▷filter/mod.rs◁──────┬┬┼───────┤│ │ │││││ ││││││││││││││││ ││ │ │││ │││ │ │││││ ││││││││││││││││ ││ ├▷filter/and_then.rs┤││ │││ │ │││││ ││││││││││││││││ ││ ├▷│filter/or_else.rs┘││ │││ │ │││││ ││││││││││││││││ ││ ├▷││filter/recover.rs┘│ │││ ├───────────────────────────────▷│││filter/service.rs◁──────┼─┤ │ │││││ ││││││││││││││││ ││ ├▷││││filter/then.rs──┤ │││ │ │││││ ││││││││││││││││ ││ ├▷│││││filter/unify.rs┘ │││ │ │││││ ││││││││││││││││ ││ ├▷││││││filter/untuple_one.rs┤││ │ │││││ ││││││││││││││││ ││ │ │││││││ │││ ├───────────────────────────────────────▷reply.rs◁───┬──────────┐ ├───────────────────────────────────────▷│route.rs───│──────┤││ │ │ │││││ ││││││││││││││││ ││ │ │││││││ │ │ │││ │ ├──────────────────────────────────────────▷server.rs◁────────┤ │ │ │││││ ││││││││││││││││ ││ │ │││││││ │ │ │ │││ │ ├────────────────────────────────────────────▷tls.rs─┴──────┘││ │ │ │││││ ││││││││││││││││ ││ │ │││││││ │ │ │ ││ │ ├──────────────────────────────────────────────▷filters/ws.rs◁│ │ ├──────────────────────────────────────────────▷│transport.rs││ │ │ │││ │ ││││││││││││││││ ││ │ │││││││ │ │ │ │ ││ │ ├─────────────────────────────────────────────────▷generic.rs││ │ ├─────────────────────────────────────────────────▷reject.rs─┴┘ │ │ │ │ │ │ ├───────────────────────────────────────────────────▷error.rs │ └───────────────────────────────────────────────────▷redirect.rs┘
-
Is there a more practical way to let warp respond to incoming requests?
What I see on the examples for the warp crate is that the examples do this:
-
I turned The Rust Book into a crate
You might want to consider using Alacritty instead of Warp. Warp is VC-funded, macOS only, closed source, and it phones home. They also kinda stole the name of a web framework.
-
I made rust-webapp-template
warp server,
-
Help with warp routes
Hello, I'd need some help with warp routes since I'm not familiar with the framework. If somebody knows how to do this I'd appreciate very much.
-
Any Rust based forum software?
If one were to undertake a project of developing something like this, which is the best web framework for it. I did some cursory research and discovered these back-end frameworks - actix, axum, poem, salvo, warp, gotham and rocket.
-
shuttle v0.7.1 has been released (improved isolation, new supported frameworks, QOL improvements)
We've added support for the warp, salvo & thruster frameworks
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.
axum - Ergonomic and modular web framework built with Tokio, Tower, and Hyper
cargo-expand - Subcommand to show result of macro expansion
actix-web - Actix Web is a powerful, pragmatic, and extremely fast web framework for Rust.
rust-learnings - Collection of Rust learnings through implementation
Rocket - A web framework for Rust.
style - css for rust
hyper - An HTTP library for Rust
quote - Rust quasi-quoting
hyperterm - A terminal built on web technologies
style - Style Dart Backend Framework
kitty - Cross-platform, fast, feature-rich, GPU based terminal