This message is an attempt to comment on the relationship between the
various treatments of extensible records that have been referred to in
the past couple of days.
While the proposal on records for Haskell 2 that I just posted is
intended for a fairly wide Haskell audience, this one will proba
With the sudden upsurge of interest in records, and Paul's recent call
for discussion on the future of Haskell, I thought that it might be
appropriate to post the following article describing some of the
alternatives for adding records to Haskell. I originally wrote and
distributed this to a num
Martin Odersky wrote:
..
> ... A good way to look at it is by comparing the
> role of record field labels with the role of other identifiers. In ML
> this correspondence made is very clear by writing the selection of
> field "l" as "#l r", i.e. the label acts like a function
> identifier. ...
I
It seems to be the season for records -- three proposals already and
I'm going to add a fourth one! Phil Wadler, Martin Wehr and I have
recently completed a paper that describes a radical simplification of
type classes. We restrict overloading to functions that have the
instance type as first a
