pouët.net

I have got a picture that the main idea of Rust is to have a language which is memory safe and which makes it easy to write non-buggy multithread programs. But I assume that bug hunting is not so important in the context of demos (and compared to a web browser) which are non-interactive programs and functionally perfect if they just reach the credits screen without crashing.

It's not just 'not crashing', it's also the class of bugs that cause your demo to misbehave on someone else's machine, or doing subtly incorrect things because you happen to be overwriting a variable (or an uninitialized variable, or whatever).

Saw this today: nannou, a creative coding framework for Rust. Might be interesting for non size limited demos (and the LAZZERRR support).

If it is about graphics, I can recommend ggez. It was a breetze to get some graphics up and running. For audio output (writing audio samples) I found cpal also very useful. There are lots of graphics libraries for Rust already, but some are a bit bug ridden or way too much boilerplate to get something basic done.
Sadly the executables are a bit big (but at least usually statically linked), even in release mode.

Wanted to add: They are big if you work with std:: and ready made crates.

https://rust-gamedev.github.io/2019/08/18/introducing-the-rust-game-development-working-group

That can be relevant for future advances in rust demomaking.

janiorca made an article about his 4k at NOVA 2020 (Ochre) : https://www.codeslow.com/2020/07/writing-winning-4k-intro-in-rust.html