wiki:Status/GHC-7.8

Version 14 (modified by simonpj, 9 months ago) (diff)

--

Release plans for GHC 7.8

Timeline

The planned timeline for 7.8 is to have a feature freeze on the 31 August 2013, followed by a period of frantic bug fixing (interrupted by ICFP), aiming for a release during November 2013.

Tickets

We would like to fix all of the high and highest priority tickets in the 7.8.1 milestone, but there are currently a lot of them so this seems optimistic. Please feel free to take a ticket and help us!

Completed new features

The features already completed are documented in the release notes: docs/users_guide/7.8.1-notes.xml

Pending new features

The following new features are planned for 7.8. They are at varying degrees of completeness, and may not all make it in.

  • Richard Eisenberg is working on closed type families (a new feature). See NewAxioms
  • Richard Eisenberg is also working on using "roles" to finally fix #1496.

  • Pedro and Richard were working on tidying up the poly-kinded Typable story. I'm not sure what, if anything, remains to be done.
  • Geoff Mainland is working generalising the support for SSE-like instructions.
  • Unboxed Booleans. Patch just needs some polishing? Jan Stolarek is working on it. See #6135.
  • Dynamic GHCi (#3658). This is working in HEAD, and enabled if DYNAMIC_GHC_PROGRAMS=YES. Currently it's enabled by default if dynamic libraries are supported, except for FreeBSD and Windows. On FreeBSD the reason it's disabled is due to a bug in FreeBSD's rtld. This has been fixed, but we're waiting for the fix to make it into releases. This might be in time for 7.8, but certainly will be for 7.10. See #7819. On Windows, there are a couple of build time annoyances: -dynamic-too doesn't work on Windows, and linking takes a very long time when dynamic linking is used. There's no technical reason why it couldn't be enabled, though. The plan is/was to use dynamic GHCi on as many platforms as possible in 7.8, and to remove support for non-dynamic-ghci in HEAD soon after. See discussion in #8039, however.