Jay Oster

This is fixed in the `invaders` example with a fixed time step and sleeping the main thread to cap the frame rate: https://github.com/parasyte/pixels/blob/3968c9748a8699a962b144118cea4bac1005ba2d/examples/invaders/src/main.rs#L161-L166

`pixels` doesn't integrate directly with any windowing provider (like `winit` or `sdl2`), If you want to resize the window, you need to use the API supported by your window provider....

Ok. It would just be a fixed scaling factor instead of dynamic (based on window inner size). This can be done.

You can add a dependency on `wgpu` in your crate, even if it is otherwise unreferenced. I'm not opposed to adding features, though.

Related: #2080

FWIW, I was looking for a way to do something similar and settled on implementing `FromStr` for an enum option. Something like this: ```rust use gumdrop::Options; use thiserror::Error; #[derive(Debug, Options)]...

It looks like `std` needs to be built with ASan, as well. Building with the `build-std` flag causes the failure to occur on Linux. The same workaround posted for macOS...

I had the same need, and ended up just patching a vendored copy of `loom` in the meantime: ```diff diff -adupwr /Users/parasyte/other-projects/loom/src/model.rs loom/src/model.rs --- /Users/parasyte/other-projects/loom/src/model.rs 2020-09-21 02:58:40.000000000 -0700 +++ loom/src/model.rs...

Semi-related: Perhaps it would be nice to support [`cint`](https://docs.rs/cint) for color interoperability with other crates?

If my preference is at all useful here, I would like `chrono` behind a feature flag if you intend to add it again. The project where I use `toml_edit` already...