gecs VS winsafe

Sure, if you'll forgive me again for copying over text from a previous post. For context, I'm the author of gecs, which is a compile-time library for generating Entity Component System worlds and performing queries against them during compilation. Over the course of writing this library I encountered a number of limitations of Rust's compile-time capabilities with generics and both declarative and proc macros. Some of them I managed to push through with hacks, but others are simply impossible to solve (at least, as far as I can tell after expending a lot of effort trying) on stable.

I disagree with this. They're a code generation tool, but not particularly powerful compared to the features I mentioned in C++. They have no understanding of types, can't evaluate constants, can't enforce constraints, can't (easily) determine build configuration in their host crate (via #[cfg]), and so on. There's also no concept of stateful proc macros or proc macro dependencies that pass information to one another. I've been working on a compile-time ECS library (source code here) and it has been a struggle in quite a number of ways.

I know all that shit because I'm the author of Rust's WinSafe library, which is a safer Rust layer over native Win32, so I had to deal with a lot of shit like this.

[dependencies] winsafe = { git = "https://github.com/rodrigocfd/winsafe", features = ["kernel"] }

Externally, you can write a lot of native Windows stuff in Rust already. Personally, I'm having a lot of fun with WinSafe.

If you had such problems (which I also had in the past), I'm really interested in you opinion about WinSafe, and if it could help you solving them.

If you're after a native Windows application, WinSafe may suit your needs.

As the author of WinSafe, I can say it's tedious sometimes, but it's often very challenging, because you have to translate crazy unsafe behaviors into Rust's ownership model. It's surely hard, but also very rewarding at the end.

As the author of the WinSafe lib, I wholeheartedly agree.

I don't know how rare this is (or how rare it should be), but this issue warned me about this potential problem, and I had to make a huge refactoring to treat the possibility. I had to rethink many aspects of all handle implementations. It was hard work, but in the end it was worth it.

WinSafe says hello.

WinSafe, for example (which attemps to be a safe layer over the Windows API), provides lots of RAII automations. A fine example is the BeginPaint function: