[m-dev.] for discussion: stream library v2

[Michael Day]

> Umm, I'm not sure I'm happy with this being restricted to chars.  At
> the very least, bytes would be better.

Perhaps time to add a byte type to the standard library? Or an integer
type class with instances of various bitsizes?

> Are we not worried about generalising to arbitrary stream types?  For
> example, I might want to treat a lexer as an input stream of tokens.

Hmm I believe that leads swiftly to multiparameter type class hell; isn't
this one of the situations in which those functional dependencies would
come in handy?

Seems like it's worth making an improvement on the current status quo
subject to revision at a later date when the capabilities of type classes
have expanded somewhat.

Michael


--------------------------------------------------------------------------
mercury-developers mailing list
Post messages to:       mercury-developers at cs.mu.oz.au
Administrative Queries: owner-mercury-developers at cs.mu.oz.au
Subscriptions:          mercury-developers-request at cs.mu.oz.au
--------------------------------------------------------------------------