Between vague documentation, decades of compatibility hacks, hacks on top of those hacks, a fundamentally different file and process model to POSIX, and the occasional toolchain bug, the amount of effort necessary to truly *support* Windows seems nothing short of herculean.
-
-
Prikaži ovu nit
-
Thankfully, I have the benefit of Phyx, GHC's resident Windows expert; however, even with his help trying to get GHC's Windows CI infrastructure to reliably pass has taken weeks and the end still seems a point on the horizon.
Prikaži ovu nit -
Perhaps the most shocking discovery of this entire ordeal is that it is literally *not possible* to reliably invoke the mingw toolchain we've been using for the last decade as it uses to its use of `exec`.
Prikaži ovu nit -
At this point it is looking likely that GHC will be moving to LLVM as its native toolchain on Windows; this will hopefully allow us to bypass many of the path and process issues that we have been historically fought with. Current plan can be found here:https://gitlab.haskell.org/ghc/ghc/issues/17777 …
Prikaži ovu nit
Kraj razgovora
Novi razgovor -
-
-
Could you drop (official) Windows support?
-
I hope not!
Kraj razgovora
Novi razgovor -
-
-
This is a universal problem of maintaining cross-platform software. As a Windows-first OSS maintainer, I have difficulties in the opposite direction. (e.g. mac OS has far more API churn than Windows, and it would be difficult to argue that Apple docs are better than MSDN.)
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
I don't use Windows, but I'm grateful that you put in the effort to keep support for such legacy operating systems in GHC, as it means my Haskell code will work there!
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.