In Prod LLVM release branch 515643669.1 ( cl/517696539 ) the experimental coroutines implementation is dropped. The `experimental/coroutines` header is removed.
Nearby doesn't use coroutines, but it uses libraries that depend on the existence of coroutine function definitions. Specifically, WinRT needs certain coroutine function definitions in order to compile.
Ordinarily, WinRT relied on the coroutine function definitions provided in the MSVC STL' `experimental/coroutines` header. The introduction of libc++ complicated this dependency for Nearby, because libc++' `experimental/coroutines` header took the place of the MSVC version, and (correctly, for C++17) provided none of the coroutine function definitions.
To resolve these issues, we implemented a patch of WinRT. The patch provided placeholder definitions, which allowed WinRT to pass compilation. This patch was submitted in cl/495104919. The patch was necessary to enable the Nearby migration from MSVC STL to libc++.
--
The removal of `experimental/coroutines` from libc++ makes this patch unnecessary. However, the patch will not compile without libc++' `experimental/coroutines` header.
The presence of libc++' `experimental/coroutines` header had prevented the corresponding MSVC STL' header from defining the functions for which the patch makes placeholders. Without the libc++' `experimental/coroutines` header, the MSVC STL header is employed and makes these definitions. The patch then redefines these functions, which causes a compilation failure.
--
This CL makes two changes: 1) It eliminates the patch, and 2) It eliminates the libc++ `experimental/coroutines` file from the Lexan libc++ distribution. This allows Nearby to function identically before and after the release of Lexan 515643669.1.
This change prevents a break from occurring when Lexan 515643669.1 is released.
PiperOrigin-RevId: 518119913
From the crash call stack, the app crashed at the line `windows_socket = nullptr;` This is because the previous line `windows_socket_.Close();` has already released all unmanaged resources associated with the StreamSocket object.
https://learn.microsoft.com/en-us/uwp/api/windows.networking.sockets.streamsocket.close?view=winrt-22621#remarks
By RAII, assigning `windows_socket_` to nullptr is equivalent to calling `delete` on the StreamSocket allocated on the heap again, which results in null pointer exception `Exception infoEXCEPTION_ACCESS_VIOLATION_READ @0x00000000` because it has already been released in the previous line by Close().
PiperOrigin-RevId: 508454142
Guogang Li