From: Christopher Allan Webber <cwebber@dustycloud.org>
To: Chris Vine <chris@cvine.freeserve.co.uk>
Cc: guile-devel@gnu.org
Subject: Re: Asynchronous event loop brainstorm at FSF 30
Date: Tue, 17 Nov 2015 11:46:24 -0600 [thread overview]
Message-ID: <87io505xhy.fsf@dustycloud.org> (raw)
In-Reply-To: <20151004171540.7a4eeb3c@bother.homenet>
Chris Vine writes:
> It is certainly the case that mixing threads with coroutines is usually
> best avoided, otherwise it becomes very difficult to know what code
> ends up running in which particular thread and thread safety becomes a
> nightmare. However, it would be good to allow a worker thread to post
> an event to the event loop safely, whereby the handler for the posted
> event would run in the event loop thread. asyncio allows this.
>
> Although not particularly pertinent to this proposal, which looks
> great, I use coroutines implemented with guile's delimited
> continuations for a minimalist "await" wrapper over glib's event loop
> as provided by guile-gnome (the whole thing is about 20 lines of code),
> which appears (to the user) to serialize the GUI or other events posted
> to the event loop. When I don't want to use guile-gnome, which is most
> of the time, I have my own (also minimalist) thread-safe event loop
> using guile's POSIX wrapper for select.
>
> My uses of guile are pretty undemanding so as I say these are
> minimalist. Something like asyncio for guile would be very nice indeed.
>
> Chris
This sounds very interesting... is the source available? Could you
point to it?
Thanks!
- Chris
next prev parent reply other threads:[~2015-11-17 17:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-03 22:29 Asynchronous event loop brainstorm at FSF 30 Christopher Allan Webber
2015-10-04 13:24 ` Amirouche Boubekki
2015-10-04 15:19 ` Christopher Allan Webber
2015-10-04 15:24 ` Christopher Allan Webber
2015-10-04 15:58 ` Nala Ginrut
2015-10-04 16:15 ` Chris Vine
2015-11-17 17:46 ` Christopher Allan Webber [this message]
2015-11-18 10:26 ` Chris Vine
2015-11-18 14:37 ` Christopher Allan Webber
2015-11-19 13:27 ` Chris Vine
2015-11-18 12:44 ` Mikael Djurfeldt
2015-11-18 14:16 ` Christopher Allan Webber
2015-11-18 16:36 ` Mikael Djurfeldt
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87io505xhy.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=chris@cvine.freeserve.co.uk \
--cc=guile-devel@gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).