Dear all,
I have looked through the tickets of haskell-prime. I would like to bring
up my own point of view concerning one specific ticket, namely Class
Aliases. I have looked at the ticket and right now it's marked as a low
priority with low probability of entering the standard.
As I see it, class aliases have a low impact on most of the code, only
requiring some syntactical changes and some extensions in .hi interface.
However, they can be very empowering with regards to the modularisation of
type classes. Often people on #haskell want to implement some subset of Num
and reuse as much as possible that which exists but find themselves stuck
because their type does not support all the semantics of Num. With the use
of type-classes one can easily decompose Num into a set of subclasses
without making it more difficult to use for the general user of Num. In
addition it can be used for other modularisations as well, making them quite
trivlal, for instance the proposal to split Enum.
Just my two cents :)
With regards,
Christophe Poucet
--
Christophe Poucet
Ph.D. Student
Phone:+32 16 28 87 20
E-mail: Christophe.Poucet at imec.be
IMEC vzw – Register of Legal Entities Leuven VAT BE 0425.260.668 –
Kapeldreef 75, B-3001 Leuven, Belgium – www.imec.be
*****DISCLAIMER*****
This e-mail and/or its attachments may contain confidential information. It
is intended solely for the intended addressee(s).
Any use of the information contained herein by other persons is prohibited.
IMEC vzw does not accept any liability for the contents of this e-mail
and/or its attachments.
**********
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.haskell.org//pipermail/haskell-prime/attachments/20060522/dfeb8a4e/attachment-0001.htm