You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<!-- Do not remove this test for UTF-8: if ??? doesn?t appear as greek uppercase omega letter enclosed in quotation marks, you should use an editor that supports UTF-8, not this one. -->
<!-- Read this before publishing packages to chocolatey.org: https://github.com/chocolatey/chocolatey/wiki/CreatePackages -->
6
+
<id>ghc</id>
7
+
<title>GHC</title>
8
+
<version>8.8.3</version>
9
+
<authors>GHC Team</authors>
10
+
<owners>Tamar Christina</owners>
11
+
<summary>GHC is a state-of-the-art, open source, compiler and interactive environment for the functional language Haskell.</summary>
12
+
<description>Highlights:
13
+
• GHC supports the entire Haskell 2010 language plus a wide variety of extensions.
14
+
• GHC has particularly good support for concurrency and parallelism, including support for Software Transactional Memory (STM).
15
+
• GHC generates fast code, particularly for concurrent programs. Take a look at GHC's performance on The Computer Language Benchmarks Game.
16
+
• GHC works on several platforms including Windows, Mac, Linux, most varieties of Unix, and several different processor architectures. There are detailed instructions for porting GHC to a new platform.
17
+
• GHC has extensive optimisation capabilities, including inter-module optimisation.
18
+
• GHC compiles Haskell code either directly to native code or using LLVM as a back-end. GHC can also generate C code as an intermediate target for porting to new platforms. The interactive environment compiles Haskell to bytecode, and supports execution of mixed bytecode/compiled programs.
19
+
• Profiling is supported, both by time/allocation and various kinds of heap profiling.
20
+
• GHC comes with several libraries, and thousands more are available on Hackage.
21
+
22
+
There's an important change to path handling for Windows starting with 8.6.1.
23
+
These changes mean that Haskell programs are no longer constraint to `MAX_PATH`. So passing a long path to `openFile` will just work.
24
+
There are a few caveats to this such as you can't access `COM` devices via `COM1` etc anymore and instead need to use the full path `\\.\COM1` etc.
25
+
This is all documented https://downloads.haskell.org/~ghc/8.6.5/docs/html/users_guide/win32-dlls.html#windows-file-paths
0 commit comments