From: "Arthur A. Gleckler" <srfi@speechcode.com>
To: Shiro Kawai <shiro.kawai@gmail.com>
Cc: Mark H Weaver <mhw@netris.org>, John Cowan <cowan@ccil.org>,
guile-devel@gnu.org, srfi <srfi-121@srfi.schemers.org>
Subject: Re: [PATCH] add SRFI: srfi-121; generators
Date: Fri, 22 Jan 2021 18:18:28 -0800 [thread overview]
Message-ID: <CALnw4LLSY6dmfhXY2dGarD6_00o8eP4vxeTvRvebP5bnvWqntg@mail.gmail.com> (raw)
In-Reply-To: <CALN0JNHiQVNV8Xw=XW5LWnWxAMyH+yDNdUFAEaZKC3wkXsoiTQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 996 bytes --]
On Fri, Jan 22, 2021 at 6:15 PM Shiro Kawai <shiro.kawai@gmail.com> wrote:
> Hi Mark,
> I agree that the whole point of generators is performance. When combined
> with lazy sequences (srfi-127), it covers many typical use cases of streams
> much more efficiently.
> I've written Gauche version with performance in mind, but it depends on a
> few non-standard features and can not be used as-is. Besides, if we do go
> for performance, we need benchmark suites as well. I'm interested in
> adopting Gauche version as the reference implementation but don't know when
> I have time. If you have some code to improve the current reference
> implementation and can merge it to the repo, we can proceed gradually, I
> guess.
>
It's not a bad idea for the sample implementation to be as clear as
possible at the expense of performance. But it certainly wouldn't hurt to
have a supplemental document making recommendations about possible
performance improvements, or even a second implementation.
[-- Attachment #2: Type: text/html, Size: 1324 bytes --]
next prev parent reply other threads:[~2021-01-23 2:18 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 [this message]
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
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=CALnw4LLSY6dmfhXY2dGarD6_00o8eP4vxeTvRvebP5bnvWqntg@mail.gmail.com \
--to=srfi@speechcode.com \
--cc=cowan@ccil.org \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.org \
--cc=shiro.kawai@gmail.com \
--cc=srfi-121@srfi.schemers.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).