Rocket 0.5 Released together with RWF2, a nonprofit organization designed to support Rocket and the surrounding ecosystem, financially and organizationally.

Check out Blade: it's a purely ray-traced renderer, with asset pipeline and egui integration, built on top of a thin low-level GPU abstraction.

I've just released blade-graphics-0.3, blade-render-0.2, and other associated crates. I believe it's now usable externally, and I'm dogfooding it myself.

Major rendering additions:

• tangent space generation and normal mapping
• spatio-temporal reservoir resampling (ReSTIR)
• environment map importance sampling, it can load EXR and HDR
• Spatio-temporal variance-guided de-noising (SVGF)

In addition, shaders are now considered assets and can have includes, shared enums and bitflags with your Rust code. The "scene" example is practically a scene editor: it allows dropping new objects, manipulating them via egui-gizmo, in addition to configuring the rendering.

The Prettier Bounty is a challenge to write a prettier-compliant pretty printer in Rust

I love browsing crates.io and blessed.rs for interesting and useful crates to experiment with. What are your favorite?

I'm especially interested in those simple ones that do one thing and do it will, like uuid, tempfile, and notify.

Greetings to all.

I have spent the last couple of evenings learning about Rust and trying it out. Wrote a simple cli calculator as a first thing and thought I would improve it by making it available over http.

I was actually a bit surprised to find that there was no http tooling in the standard library, and searching online gave me an overload of information on different libraries and frameworks.

I ended up implementing my own simple HTTP server, might as well as this is a learning project.

Now I have it working, and while it isn't perfect or done, I thought that this would be a good time to check what things I am doing wrong/badly.

Which is why I am here, would love to get some pointers on it all to make sure I am going in the right direction in the future.

The project is hosted here: https://github.com/Tebro/rsimple_http

This is a #[no_std]-friendly library for encoding and decoding WebSocket frames.

It does not offer full WebSocket experience like Tungstenite, only the part where you need to deal with bits and bytes.

It works completely without using memory allocator. You meed to assemble WebSocket messages chunk by chunk yourself though.

Low-level HTTP 1 and 2 processing library "hyper" gets released.

It contains fewer features than 0.14, (relatively) "high-level" client and server are gone. Only hyper::{client,server}::conn remain.

Also there is some IO abstraction: though it still depends on Tokio (only the sync feature), it should be easier to connect other runtimes. Just using it with Tokio like before is though less straightforward.

Do not hurry to upgrade your project from 0.14 to 1, better wait for better support in the ecosystem.

Author of Pomsky here. Feel free to ask me anything!

Hi! I tried out yew last night and was going through the tutorial (the link). At the end the tutorial is using a link to an external resource. My guess is that the tutorial app shall create a website with a list of (empty) videos that is created by reading an external json-file from the yew-website. The problem is that this doesn't work for me, the list stays empty. I also don't find the full source of this example somewhere. On the site it is only iteratively described. I am pretty sure I have everything like on the website.

We now run part of the tests in the Rust repo's CI, which is the first step to eventually distributing the GCC codegen via rustup! We also improved a lot the cross-compilation situation.

I am pretty new to Rust and I find the docs can be a little confusing sometimes so I'd be really thankful for people who can help me understand this.

So for my uni project we are doing part of it in Rust. and I am having issues understanding how the modules function. So here is my example program.

Main.rs does some stuff and then passes a pointer into a function from a separate Rust file. That function then does some more things and passes a new variable into a function form another separate Rust file as a pointer.

main.rs has mod separate_file1; and then in separate_file 1 there is a mod separate_file2;.

The confusion is that separate_file2 does not read from the same directory as main.rs despite being in it. Instead it looks in a sub-folder under the same name.

If someone could explain to me why it works like this and what the best practice is for using modules I would be really thankful. It's made me struggle a lot.