unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: 01/02: Re-implement (ice-9 streams) in terms of (srfi srfi-41)
Date: Tue, 10 Mar 2015 22:58:00 -0400	[thread overview]
Message-ID: <8761a81brb.fsf@netris.org> (raw)
In-Reply-To: <E1YUxAA-0001qR-DN@vcs.savannah.gnu.org> (Andy Wingo's message of "Mon, 09 Mar 2015 12:52:02 +0000")

Andy Wingo <wingo@pobox.com> writes:

> wingo pushed a commit to branch master
> in repository guile.
>
> commit aead655a45e689b332cfd148ecbb6d764e2c8eb8
> Author: Andy Wingo <wingo-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
> Date:   Thu Mar 5 09:44:53 2015 +0100
>
>     Re-implement (ice-9 streams) in terms of (srfi srfi-41)
>     
>     * module/ice-9/streams.scm: Re-implement in terms of SRFI-41.  Passes
>       tests.

I think we can't do this because (ice-9 streams) are based on native
Guile promises which provide built-in thread synchronization, whereas
SRFI-41 streams are based on SRFI-45 promises which do not include
thread synchronization.

I vaguely remember finding that SRFI-45 promises (written in pure
Scheme) performed better than native Guile promises (written in C),
presumably because of the lack of built-in thread synchronization.  I
don't remember what platform I did those comparisons on.

     Mark



       reply	other threads:[~2015-03-11  2:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150309125201.7033.46022@vcs.savannah.gnu.org>
     [not found] ` <E1YUxAA-0001qR-DN@vcs.savannah.gnu.org>
2015-03-11  2:58   ` Mark H Weaver [this message]
2015-03-11  8:30     ` 01/02: Re-implement (ice-9 streams) in terms of (srfi srfi-41) Andy Wingo
2015-03-29 17:20       ` Ludovic Courtès
2015-03-29 23:54         ` Mark H Weaver
2015-03-30  8:03           ` Ludovic Courtès

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=8761a81brb.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guile-devel@gnu.org \
    --cc=wingo@pobox.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).