Re-export winit

[junderw]

There are a lot of public exposed APIs that accept and return winit types (ie):

glium/src/backend/glutin/mod.rs

Line 333 in 1676f0d

pub fn build(self, event_loop: &winit::event_loop::EventLoop<()>) -> (winit::window::Window, Display<glutin::surface::WindowSurface>) {

Also, most of the tutorials make heavy use of the winit APIs.

Currently this requires users to figure out which version of winit is currently being used, and make sure their winit dependency stays in sync with the glium dependency, otherwise it will be a breaking change if your API expects a 0.29 EventLoop when the user is still using a 0.28 EventLoop.

It seems like you are aware of this, and are bumping semver minor to signify pre-1.0.0 breaking changes whenever you bump the winit dependency to a breaking change.

Since that is already a requirement on your library, you might as well re-export winit explicitly and change the tutorials to recommend using the re-export.

[est31]

Good point. Before, glutin did this for us, which we already export from the backend::glutin module. From that module, we could also export the winit dependency.