On Tue, 2007-05-01 at 20:54 -0400, Chris King wrote:
> On 5/1/07, skaller <[EMAIL PROTECTED]> wrote:
> > ** In the end, i hope to merge classes, typeclasses
> > and modules into a single 'class' construction.
>
> Yay!
>
> > typeclasses with variables (not just type variables)
> > make sense .. th
On 5/1/07, skaller <[EMAIL PROTECTED]> wrote:
> ** In the end, i hope to merge classes, typeclasses
> and modules into a single 'class' construction.
Yay!
> typeclasses with variables (not just type variables)
> make sense .. the functions are just methods and the
> variables live in an dynamical
On Tue, 2007-05-01 at 12:14 -0700, Erick Tryzelaar wrote:
> skaller wrote:
> > should work. Or perhaps:
> >
> > const inf: double = "1.0/0.0";
>
> I'd prefer that. I wish we could do this, but it doesn't compile because
> of the "virtual const".
That's a bug. I tried to make it work, but i
skaller wrote:
> should work. Or perhaps:
>
> const inf: double = "1.0/0.0";
I'd prefer that. I wish we could do this, but it doesn't compile because
of the "virtual const".
typeclass Floating[T] {
virtual const inf: T;
virtual fun isinf: T -> bool;
}
instanc
On Fri, 2007-04-27 at 19:42 -0700, Erick Tryzelaar wrote:
> So it looks these values are matchable, but they aren't defined so that
> you can do "print inf; endl". Can we still match against a NaN or an inf
> if we replace these with typeclass functions?
Don't know: we should review for 1.1.4. I
So it looks these values are matchable, but they aren't defined so that
you can do "print inf; endl". Can we still match against a NaN or an inf
if we replace these with typeclass functions?
I could see it useful to be able to have a numeric_limits-like typeclass
to provide this kind of metadata
