unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Linus Björnstam" <linus.bjornstam@veryfast.biz>
To: "Marc Nieper-Wißkirchen" <marc@nieper-wisskirchen.de>
Cc: Shiro Kawai <shiro.kawai@gmail.com>, John Cowan <cowan@ccil.org>,
	guile-devel@gnu.org, Mark H Weaver <mhw@netris.org>,
	"Arthur A. Gleckler" <srfi@speechcode.com>,
	srfi <srfi-121@srfi.schemers.org>
Subject: Re: [PATCH] add SRFI: srfi-121; generators
Date: Tue, 26 Jan 2021 12:54:18 +0100	[thread overview]
Message-ID: <4f5c2aac-78fb-496c-9d9c-89500ebd1487@www.fastmail.com> (raw)
In-Reply-To: <CAEYrNrS5MBvsQSCBEsQDwsa1540_bdO4zRHt=2neF56EAz+HyQ@mail.gmail.com>

The code's internet presence is apparently gone (bitbucket mercurial. I don't know how I missed that ). I won't have access to that code for about 2 weeks, but I will upload it and try to get it up to par with the updated SRFI-158.

Lg. Linus Björnstam

On Tue, 26 Jan 2021, at 08:14, Marc Nieper-Wißkirchen wrote:
> Am Di., 26. Jan. 2021 um 08:08 Uhr schrieb Linus Björnstam 
> <linus.bjornstam@veryfast.biz>:
> > Hi Y'all!
> > 
> > I have an efficient, almost done implementation of srfi-121. I believe it lacks generator-unfold, but that is all. make-coroutine-generator is implemented using delimited continuations and runs a lot faster than the one in the reference implementation, with the caveat that it is apparently slightly incompatible: the coroutine generator usage in (srfi 146 hash) yielded the wrong result - despite my version passing all tests.
> 
> Can you post a MWE?
>



  reply	other threads:[~2021-01-26 11:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21 18:39 [PATCH] add SRFI: srfi-121; generators John Cowan
2021-01-23  0:58 ` Mark H Weaver
2021-01-23  2:14   ` Shiro Kawai
2021-01-23  2:18     ` Arthur A. Gleckler
2021-01-23  6:37       ` Mark H Weaver
2021-01-26  3:29         ` John Cowan
2021-01-26  6:48           ` Linus Björnstam
2021-01-26  6:49             ` Linus Björnstam
2021-01-26  7:14             ` Marc Nieper-Wißkirchen
2021-01-26 11:54               ` Linus Björnstam [this message]
2021-04-08 15:53                 ` Arthur A. Gleckler
2021-04-11  6:52                   ` Linus Björnstam
2021-04-11 16:17                     ` Arthur A. Gleckler
     [not found] <mailman.61.1596470427.10776.guile-devel@gnu.org>
2020-08-03 19:41 ` Marc Nieper-Wißkirchen
2020-08-04 12:48   ` Marc Nieper-Wißkirchen
2020-08-04 15:24   ` John Cowan
2020-08-04 15:58     ` Marc Nieper-Wißkirchen
2020-08-04 17:24       ` Dr. Arne Babenhauserheide
  -- strict thread matches above, loose matches on Subject: below --
2020-08-01  3:42 John Cowan
2020-08-02 22:39 ` Mark H Weaver
2019-07-01  0:09 nly
2019-07-01  5:06 ` Mark H Weaver
2019-07-01  6:00   ` Mark H Weaver
2019-07-01  6:21     ` Amar Singh

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=4f5c2aac-78fb-496c-9d9c-89500ebd1487@www.fastmail.com \
    --to=linus.bjornstam@veryfast.biz \
    --cc=cowan@ccil.org \
    --cc=guile-devel@gnu.org \
    --cc=marc@nieper-wisskirchen.de \
    --cc=mhw@netris.org \
    --cc=shiro.kawai@gmail.com \
    --cc=srfi-121@srfi.schemers.org \
    --cc=srfi@speechcode.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).