mitchmindtree

I'm going to publish the crate as 1.0.0 for now, but may add an `ffi` module in the future if I get the time.

> If you still have to handle HardFaults, why bother going through the extreme pain of trying to get rid of Rust panics? Great point @Dirbaio - and slightly terrifying!...

## `#[allow_panic]`? A possible alternative approach to progressively adding `#[no_panic]` everywhere might be to do the opposite and disallow panicking by default somehow (via `panic-never` or otherwise), but provide an...

Thanks for your insight @ryan-summers! I just want to add/get a bit of clarification on some points: ### Moving `panic!`s to error handling > > I cannot tell you how...

> I'm not quite sure why bound checks seem to be deemed the largest cause of undesirable panic causes I didn't mean to imply that it's difficult to work around...

@seqizz we might be better off creating a module option (see [here](https://nixos.wiki/wiki/Module) for info about module structure) for specifying either one in the configuration.

@Boscop conrod's `glium` feature (as used in the [glutin_glium.rs](https://github.com/PistonDevelopers/conrod/blob/master/examples/glutin_glium.rs) example) may be more suited to your use if you're mixing conrod GUI into a plugin like this one frame at...

Ah yes, I see the issue there. I think it'd still be nice to encapsulate this in a variant for piston_window's `Error` enum so that it's a little clearer where...

@bvssvni I remember talking to you a long time ago and mentioning the idea that it would be really nice if there was a simple crate which just picked one...

I like the idea of adding some sort of `flag` or `mode`. It might even be useful to switch between both `mode`s at runtime (i.e. a game's main menu vs...