* [Caml-list] Haskell class type simulation
@ 2002-11-21 21:13 Johan Baltié
2002-11-21 21:45 ` kahl
0 siblings, 1 reply; 2+ messages in thread
From: Johan Baltié @ 2002-11-21 21:13 UTC (permalink / raw)
To: caml-list
Hi !
I'm currently looking for a way to simulate the Haskell "class type" notion
in OCaml i.e. the same kind of :
class Eq a where
(==), (/=) :: a -> a -> Bool
class (Eq a) => Ord a where
compare :: a -> a -> Ordering
(<), (<=), (>=), (>) :: a -> a -> Bool
max, min :: a -> a -> a
For me it's a bit like module signature with an abstract type and an
"extending" semantic and a type constraint.
Any hint ?
--
Ciao
Jo
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Caml-list] Haskell class type simulation
2002-11-21 21:13 [Caml-list] Haskell class type simulation Johan Baltié
@ 2002-11-21 21:45 ` kahl
0 siblings, 0 replies; 2+ messages in thread
From: kahl @ 2002-11-21 21:45 UTC (permalink / raw)
To: johan.baltie; +Cc: caml-list
<johan.baltie@wanadoo.fr> wrote:
>
> I'm currently looking for a way to simulate the Haskell "class type" notion
> in OCaml i.e. the same kind of :
>
> class Eq a where
> (==), (/=) :: a -> a -> Bool
>
> class (Eq a) => Ord a where
> compare :: a -> a -> Ordering
> (<), (<=), (>=), (>) :: a -> a -> Bool
> max, min :: a -> a -> a
>
> For me it's a bit like module signature with an abstract type and an
> "extending" semantic and a type constraint.
We looked the other way in:
@InProceedings{Kahl-Scheffczyk-2001,
author = {Wolfram Kahl and Jan Scheffczyk},
title = {Named Instances for Haskell Type Classes},
booktitle = {Proc.\null{} Haskell Workshop 2001},
year = {2001},
editor = {Ralf Hinze},
volume = {59},
number = {2},
series = ENTCS,
note = {See also: \textsf{http://ist.unibw-muenchen.de/Haskell/NamedInstances/}},
abstract = {Although the functional programming language Haskell
has a powerful type class system,
users frequently run into situations
where they would like to be able to define or adapt
instances of type classes
only \emph{after} the remainder of a component has been produced.
However, Haskell's type class system
essentially only allows late binding
of type class constraints on free type variables,
and not on uses of type class members
at variable-free types.
In the current paper we propose a language extension that
enhances the late binding capabilities of Haskell type classes,
and provides more flexible means for type class instantiation.
The latter is achieved via \emph{named instances}
that do not participate in automatic context reduction,
but can only be used for late binding.
By combining this capability with the automatic aspects
of the Haskell type class system,
we arrive at an essentially conservative extension
that greatly improves flexibility of programming
using type classes and opens up new structuring principles
for Haskell library design.
We exemplify our extension
through the sketch of some applications
and show how our approach could be used
to explain or subsume other language features
as for example implicit parameters.
We present a typed lambda-calculus for our extension
and provide a working prototype type checker on the basis of
Mark Jones' ``Typing Haskell in Haskell''.}
}
Best regards,
Wolfram
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-11-21 21:37 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-11-21 21:13 [Caml-list] Haskell class type simulation Johan Baltié
2002-11-21 21:45 ` kahl
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox