When user wants to deal with platform specific code they most of the time need raw display, like e.g. wl_display. However RawWindowHandle provides with both of them.
I'd suggest to logically split them into RawDisplayHandle and RawWindowHandle, where RawDisplayHandle would have only reference to display and RawWindowHandle could have only window, like wl_surface or be the way it is right now?
The issue I'm having is that I want Display on every platform, but I don't want surface, since the surface isn't yet created.
For example winit could implement raw_display_handle on event loop, so I can pass to e.g. glutin.
When user wants to deal with platform specific code they most of the time need raw display, like e.g. wl_display. However RawWindowHandle provides with both of them.
I'd suggest to logically split them into
RawDisplayHandleandRawWindowHandle, whereRawDisplayHandlewould have only reference to display andRawWindowHandlecould have only window, likewl_surfaceor be the way it is right now?The issue I'm having is that I want Display on every platform, but I don't want surface, since the surface isn't yet created.
For example winit could implement
raw_display_handleon event loop, so I can pass to e.g. glutin.