egl: remove cfg from code not needing them

[kchibisov]

--

@MarijnS95 I think something like that?

[MarijnS95]

I also wonder if we need optimizations like:

glutin/glutin/src/api/egl/config.rs

Lines 330 to 347 in 5a7783c

	#[cfg(not(any(wayland_platform, x11_platform)))]
	fn supports_transparency(&self) -> Option<bool> {
	None
	}
	#[cfg(any(wayland_platform, x11_platform))]
	fn supports_transparency(&self) -> Option<bool> {
	use raw_window_handle::RawDisplayHandle;
	match *self.inner.display.inner._native_display? {
	#[cfg(x11_platform)]
	RawDisplayHandle::Xlib(_) | RawDisplayHandle::Xcb(_) => {
	self.x11_visual().map(|visual| visual.supports_transparency())
	},
	#[cfg(wayland_platform)]
	RawDisplayHandle::Wayland(_) => Some(self.alpha_size() != 0),
	_ => None,
	}
	}

This should compile down to match ...? { _ => None } which can only ever return None anyway.

[kchibisov]

that's to avoid clippy lints and is easier to read.

[MarijnS95]

Didn't we typically disable that lint because this "single match arm" occurs in many more places in glutin?

I don't find the (negated) cfgs particularly easy to read nor modify when new variants ever need to be added.

[kchibisov]

We don't disable it and it's never triggered., you can grep for it

[kchibisov]

Seems like clippy doesn't complain about it, so I guess it's fine.