Does this fit the scope of wio-rs?

terrybrash commented 8 years ago

I've got my own safe wrappers for winapi-rs: https://github.com/brashaw/C4/blob/master/src/win32/safe.rs

I will clean it up and move it into wio-rs if it's welcome.

retep998 commented 8 years ago

Typically I've been following the principle of wrapping winapi types in safe wrappers. So instead of working with a console HANDLE directly, I have it wrapped up in a ScreenBuffer. Instead of handing out a COORD, I'd give out (i16, i16), although I really ought to change that to be two structs Point and Size. You seem to have a lot of freestanding functions which take and return raw things directly, so it would definitely take a bit of refactoring to get it into the style I've been going for. You're free to do so if you want.

terrybrash commented 8 years ago

You're right; I don't think my code will fit then.

My goals are to:

hide the unsafe code
provide correct error handling
keep the function signatures as true to the win32 functions they're calling as possible (which is why the raw types are mixed in there)

For my purposes, I don't mind working with the raw types directly. I just needed a safe way to work with them.

retep998 / wio-rs

Does this fit the scope of wio-rs? #8