Haskell 1.3 nearly ready

The Haskell 1.3 effort is nearly complete. Although a new report is not yet complete, all proposed changes to the language as well as the new Prelude are now available for public comment. These documents are available on the web at http://www.cs.yale.edu/HTML/YALE/CS/haskell/haskell13.html An

Changes in Haskell 1.3 since last posting

If you have looked at the Haskell 1.3 material previously, the main difference is that all issues regarding records have finally been resolved. In addition, a number of smaller changes have been made: `module M' is used in export lists instead of `M..' The text of the new Prelude is now includ

Re: Changes in Haskell 1.3 (Qualified names)

The proposed change should not break too much code. The `.' is only treated specially after a constructor. This will break: tstpatp9= (P_cons P_write.P_cons P_read) P_empty_list because of the P in P_write but this will be fine: proc_emulator f = prm_em.f Since constructors appear r

Re: adding instances to (,)

Your error messages from ghc are correct: you have violated the infamous C-T rule (section 4.3.2, page 32) which restricts instance declarations to the module containing either the class or the datatype. Since (,) and Num are both in the prelude, you can't compile this in official Haskell 1.2.

1.3 report available from Yale

You can also get the 1.3 report from Yale via ftp: on haskell.cs.yale.edu look in pub/haskell/report. John

Prelude Problems

Ignoring the issue of whether the current Prelude would be improved using a more general class heirarchy, let me point out the real failing of Haskell here. The problem is not so much that the prelude doesn't work the way you want it to, but rather that there is no way to build your own prelude

Draft of Haskell 1.4 Report is now available

We would like to make the current draft of the Haskell 1.4 report available for public comment. To see the new report and find out about changes from Haskell 1.3 please look at http://haskell.cs.yale.edu/1.4/haskell-report.html There is not much new material in the 1.4 report - it is substanti

Preliminary Haskell 1.3 report now available

Announcing a preliminary version of the Haskell 1.3 report. The Haskell 1.3 report is nearly complete. All technical issues appear to be resolved and the report is nearly ready. The report will be finalized April 19. Any comments must be submitted by April 15. We do not anticipate making an

Re: Haskell 1.3

We are still in the middle of a bunch of minor last-minute changes. While the technical aspects of Haskell 1.3 are stable, we're still fiddling with the prelude and the wording of the report. We've now set a `final' final release date at May 1. As before, the working version of the report is ava

Status of Haskell 1.3

The Haskell 1.3 report is nearly done. The text of the report is complete - I'm working on indexing and web pages. We also have an initial cut at the Library Report. If you are interested in seeing the new report on the web, look at http://haskell.cs.yale.edu/haskell-report/haskell-report.html

Haskell 1.3 Report is finished!

The Haskell 1.3 Report is now complete. A web page with the entire report and other related information is at: http://haskell.cs.yale.edu/haskell-report/haskell-report.html This new report adds many new features to Haskell, including monadic I/O, standard libraries, constructor classes, labeled

Re: Type synonyms and coercions, again

To answer your questions ... - Is the above view of type synonyms really equivalent to the Haskell report's definition? (Above view: consider the type and it's synonym to be distinct but with implicit bidirectional coercion) Almost. In some places, synonyms are not allowed. Your sche

Comparing different Yale Haskell systems

Different Versions of Yale Haskell Compared --- There are currently three different platforms running Yale Haskell. Yale Haskell runs on Lucid Common Lisp, CMU Common Lisp, and AKCL. This document describes the differences between these