Dacode45

Two reasons. 1) So you can't use those functions in two separate threads. 2) So you know which functions mutate the underlying raylib state.

That's fair. I haven't used Clippy before and I'm not sure how to set it up. I'll have to see about that.

Going to have to look at this one more closely

I like the idea, but I don't want to build another static library. If you can make this work by including your new .h in rgui_wrapper.cpp and rgui_wrapper.h and check...

Go ahead dude. Chat on discord if you need help.

@theamazingwaffle you should create a new global struct for physac. - RaylibHandle has a lot of mutability rules so you'll be fighting the borrow checker if put physac stuff in...

That shouldn't work on stable. https://doc.rust-lang.org/std/primitive.array.html. Are you using nightly? Raylib-rs is stable only right now.

Monotonic time is an extremely hard problem. RUST actually ensures that this doesn't fail even when the underlying system call can fail. See https://doc.rust-lang.org/src/std/time.rs.html#203. For rust, it might be best...

You'll have to rebuild raylib with an older version of OpenGL. Follow the nobuild guide to use your own version of raylib. https://github.com/deltaphc/raylib-rs/wiki/Using-nobuild-feature

Could you post an example?