MaulingMonkey

unsafe_unsound_unstable_remove_static_asserts_for_coverage

3

More stable-friendly replacement for https://github.com/Lokathor/bytemuck/pull/88 Since this is a `--cfg` and not a feature, and it has a scary name, it should be quite difficult and unnecessary for libraries to...

Implement std::error::Error to ease type erasure

1

Box::from(...) is implemented by default for anything that implements Error, and `?` uses from by default, making this handy for anything dealing with multiple error types. - Since CI targets...

There's a bunch of hidden xinput functions in later XInput versions - in particular I'm wondering if you'd be interested in a PR to get XInputGetStateEx (ordinal 100) available, which...

Consider refactoring the APIs to use Future s.

1

Web MIDI support is made awkward in a couple of places by the browser's use of async/deferred callbacks: * Getting input/output device lists (need to request access first) * Opening/closing...

AsIUnknown for safer ComPtr s

2

https://github.com/retep998/winapi-rs/issues/571 originally suggested `AsRef`, and was rejected as a lot of boilerplate to merely streamline niche use cases. This PR adds minimal code to allow "properly" handling something much less...

`Display` on `StyledObject` is not working well with WinApi

5

This works fine on windows 10, but appears completely unstyled on windows 7: ```rust use crossterm::*; fn main() { println!("{} {} {}", "fore".black(), "back".on_black(), "Black"); println!("{} {} {}", "fore".dark_grey(), "back".on_dark_grey(),...

Could be nice.

Currently, I believe this results in incomplete, bogus triangulation -- better responses would be either throwing an exception or creating points and handling the case.

Seems to be due to flipping the data rather than the rendering, probably not an outright bug. I may not fix this.

Format used isn't a simple outline like the rest of the .dat files. Possibly pairs of points representing line segments?