From: tim@fungible.com (Tim Freeman)
To: caml-list@inria.fr
Subject: [Caml-list] Do streams still need to be patched?
Date: Tue, 30 Jul 2002 08:54:28 -0700 [thread overview]
Message-ID: <20020730155645.88DD47F66@lobus.fungible.com> (raw)
I see this comment at the beginning of streams.ml:
(* The fields of type t are not mutable to preserve polymorphism of
the empty stream. This is type safe because the empty stream is never
patched. *)
Is this still true? I can easily imagine that it used to be true if
and when OCAML had weak type variables, but it doesn't anymore.
If it isn't true any more, then I think it would be possible to make a version
of streams that's as fast and functional as what's there now, and it
would allow consing streams to interoperate properly with streams
derived from functions or channels.
--
Tim Freeman
tim@fungible.com
GPG public key fingerprint ECDF 46F8 3B80 BB9E 575D 7180 76DF FE00 34B1 5C78
-------------------
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
reply other threads:[~2002-07-30 15:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020730155645.88DD47F66@lobus.fungible.com \
--to=tim@fungible.com \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox