xml-mut VS winsafe

This is exactly what I needed when implementing xml-mut :D I have used roxmltree instead and manipulated text directly. will try to rewrite it using Xot.

I was developing a game with Bevy some time ago. But sadly have no time to contribute to it at this time. It still uses Bevy 0.9. Also, I have started some "thing (tm)" related to XML transformation. If that would be your jazz you could grab something like this and have a stab at it :).

Hello dear people. So I have been developing this experiment of mine. it is a simple XML mutation definition language resembling SQL with a CLI to invoke it (something instead of unwieldy XSLT). I am not a top Rust dev just yet. So I would appreciate any feedback regarding the code base. Advice welcome! Further, I would like to know if you consider it useful. Should I invent this when again?

If I will find some time to spare will work on xml-mut. A simple XML mutation definition language resembling SQL.

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: