Make Windows main thread checks more forgiving

src/changelog/unreleased.md

@@ -158,6 +158,8 @@ changelog entry.
   - In the same spirit rename `DeviceEvent::MouseMotion` to `PointerMotion`.
   - Remove `Force::Calibrated::altitude_angle`.
   - On X11, use bottom-right corner for IME hotspot in `Window::set_ime_cursor_area`.
+- Main thread check is now more lax on Windows due to it not being fully reliable: it now produces a log instead
+  of a hard panic, and is not checked without `cfg(debug_assertions)`.
 
 ### Removed
 

src/event_loop.rs

@@ -71,7 +71,7 @@ impl EventLoopBuilder {
     ///
     /// ## Panics
     ///
-    /// Attempting to create the event loop off the main thread will panic. This
+    /// Attempting to create the event loop off the main thread may log or panic. This
     /// restriction isn't strictly necessary on all platforms, but is imposed to
     /// eliminate any nasty surprises when porting to platforms that require it.
     /// `EventLoopBuilderExt::with_any_thread` functions are exposed in the relevant

src/platform_impl/windows/event_loop.rs

@@ -186,8 +186,9 @@ impl EventLoop {
     ) -> Result<Self, EventLoopError> {
         let thread_id = unsafe { GetCurrentThreadId() };
 
+        #[cfg(debug_assertions)]
         if !attributes.any_thread && thread_id != main_thread_id() {
-            panic!(
+            tracing::warn!(
                 "Initializing the event loop outside of the main thread is a significant \
                  cross-platform compatibility hazard. If you absolutely need to create an \
                  EventLoop on a different thread, you can use the \
@@ -556,10 +557,12 @@ impl rwh_06::HasDisplayHandle for OwnedDisplayHandle {
 /// to setup global state within a program. The OS will call a list of function pointers which
 /// assign values to a static variable. To have get a hold of the main thread id, we need to place
 /// our function pointer inside of the `.CRT$XCU` section so it is called before the main
-/// entrypoint.
+/// entrypoint. Note that when compiled into a dylib, this is not guaranteed to be ran from the 
+/// "main" thread, so this is not foolproof.
 ///
 /// Full details of CRT initialization can be found here:
 /// <https://docs.microsoft.com/en-us/cpp/c-runtime-library/crt-initialization?view=msvc-160>
+#[cfg(debug_assertions)]
 fn main_thread_id() -> u32 {
     static mut MAIN_THREAD_ID: u32 = 0;