make GlutinEventLoop public

[LoganDark]

• Tested on all platforms changed
• Added an entry to CHANGELOG.md if knowledge of this change could be valuable to users
• Updated documentation to reflect any user-facing changes, including notes of platform-specific behavior
• Created or updated an example program if it would help users understand this functionality

[kchibisov]

It was not intended to be public and I'm not sure what the use is. Though, sooner we'd be updating to new winit traits and majority of that will just go away.

[LoganDark]

It was not intended to be public and I'm not sure what the use is. Though, sooner we'd be updating to new winit traits and majority of that will just go away.

The use is to trivially accept either EventLoop or ActiveEventLoop to my own functions that internally call glutin's. I figured reusing your preexisting sealed trait would be easier than making my own.

[kchibisov]

The use is to trivially accept either EventLoop or ActiveEventLoop to my own functions that internally call glutin's. I figured reusing your preexisting sealed trait would be easier than making my own.

Can't the &dyn ActiveEventLoop be accepted? It's also a trait.

[LoganDark]

Can't the &dyn ActiveEventLoop be accepted? It's also a trait.

Is it?

It seems to exist in winit-core, but winit-core and winit_core are not on crates.io and the trait is not re-exported by winit. So I'm not sure how to access it :/

I also searched the entire winit dependency and the trait doesn't exist in there:

[kchibisov]

Oh, indeed. The plan is to use dyn ActiveEventLoop in the future and just winit-core here, I guess, so not sure about this PR now given that it can be just copied from here to your code base for a while?