From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: "Milan Stanojević" <milanst@gmail.com>
Cc: yminsky@gmail.com, caml-list@inria.fr
Subject: Re: [Caml-list] [ANN] Async, a monadic concurrency library
Date: Fri, 28 Oct 2011 09:29:42 +0200 [thread overview]
Message-ID: <1319786982.18639.225.camel@thinkpad> (raw)
In-Reply-To: <CAKR7PS_gfwh7Nes04TWpBdU4H9JHF9mrBXTdDU_=PD=jpFqJfA@mail.gmail.com>
Am Donnerstag, den 27.10.2011, 15:10 -0400 schrieb Milan Stanojević:
> > You probably mean the case where x has already computed a result.
>
> Yes.
>
> >
> > When developing Uq_engines, I was a bit unsure how to treat this case.
> > In the initial version, I just disallowed this case: There was simply no
> > way to run into it. If you wanted to create a thread that just yields a
>
> In Async and Lwt I think it quite possible to have this case even if x
> was not just giving you a constant value. For example, x could be
> read_char (), and if you have buffered input (like Async does, and
> probably Lwt) it is quite possible that read_char will be determined
> immediately (since there is no need to issue a system call)
Right, if functions like read_char are considered as primitives, you can
have that. In Equeue e.g. Uq_io.really_input_e isn't a primitive, but
just something built on top of input_e, and if it reads from the buffer,
the value is returned via eps_e.
So, it depends a bit on the design which functions show this phenomenon.
Gerd
--
------------------------------------------------------------
Gerd Stolpmann, Darmstadt, Germany gerd@gerd-stolpmann.de
Creator of GODI and camlcity.org.
Contact details: http://www.camlcity.org/contact.html
Company homepage: http://www.gerd-stolpmann.de
*** Searching for new projects! Need consulting for system
*** programming in Ocaml? Gerd Stolpmann can help you.
------------------------------------------------------------
next prev parent reply other threads:[~2011-10-28 7:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 0:32 Yaron Minsky
2011-10-26 5:31 ` Cedric Cellier
2011-10-26 10:40 ` Yaron Minsky
2011-10-26 7:33 ` Gerd Stolpmann
2011-10-26 10:57 ` Yaron Minsky
2011-10-26 11:18 ` rixed
2011-10-26 11:34 ` Yaron Minsky
2011-10-26 12:49 ` Jérémie Dimino
2011-10-26 12:31 ` Gerd Stolpmann
2011-10-27 17:36 ` Milan Stanojević
2011-10-27 18:34 ` Gerd Stolpmann
2011-10-27 19:10 ` Milan Stanojević
2011-10-28 7:29 ` Gerd Stolpmann [this message]
2011-10-26 8:07 ` Jérémie Dimino
2011-10-26 11:03 ` Yaron Minsky
2011-10-26 11:06 ` Mark Shinwell
2011-10-26 11:20 ` Anil Madhavapeddy
2011-10-26 11:37 ` Mark Shinwell
2011-10-29 0:52 ` oliver
2011-10-31 9:12 ` Mark Shinwell
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=1319786982.18639.225.camel@thinkpad \
--to=info@gerd-stolpmann.de \
--cc=caml-list@inria.fr \
--cc=milanst@gmail.com \
--cc=yminsky@gmail.com \
/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