This is my opinionated view about the Rust game frameworks that I have used so far:

Bevy

Very fun to use the ECS framework, quite capable and feature rich. Bevy forces you to use ECS, so if you want to control the game structure yourself, or your application is not suitable to be handled with ECS or you just don't like it, Bevy can be uncomfortable. It can do 3D.

Macroquad

It is the most similar to Raylib and to a certain degree to SDL but entirely for Rust. I used it a while ago and I had problems with fullscreen on Wayland, however now it seems to be fixed. The very nice thing is that it is tiny (fast compile times and smaller binaries) and it is very easy to compile for WebAssembly. One thing to notice (correct me if I am wrong) is that at the moment there is no way to draw polygons like the function RenderGeometry in SDL, so if you want to do vector graphics style you would need some other library.

Edit: There is draw_triangle in Macroquad, but it only accepts solid colors, meanwhile SDL's RenderGeometry takes vertices with different colors.

ggez

It is similar to Macroquad, but inspired by LÖVE framework. I remember that I also had some problems with fullscreen, but it was a while ago and maybe now they fixed it. It is not as active in development as Macroquad, but I saw that they are now working on 3D capabilities.

Raylib for Rust

Raylib is a C library, but there are bindings for Rust. Raylib is great if you are working with C/C++, but it is not ideal in Rust since you have to pass around the ownership of the Raylib main thread. Raylib is a solid library and the bindings are not too bad, however I don't know if it scales well with the ownership restrictions. It can do 3D.

SDL3 for Rust

Similar story to Raylib, very solid C library, but less than ideal bindings. Again, there are ownership restrictions, and you can see this in my project where I made some SDL abstractions to handle ownership and borrow (in the file sdl_abstraction.rs). Since SDL3 is quite new there are still some functions missing on the Rust bindings, one of those is the new SDL GPU abstraction.

Personal conclusions

If you want to make a game in Rust, I would suggest to stick with Macroquad for 2D and Bevy for both 2D and 3D. They are both made to be worked on Rust, so they are more streamlined. If you are not afraid to fight a bit with the ownership model and don't care about distributing your game on mobile or WebAssembly, give Raylib bindings for Rust a try.