From: Mark H Weaver <mhw@netris.org>
To: nly@disroot.org
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] add SRFI: srfi-121; generators
Date: Mon, 01 Jul 2019 02:00:38 -0400 [thread overview]
Message-ID: <87woh2gupl.fsf@netris.org> (raw)
In-Reply-To: <871rzaibt1.fsf@netris.org> (Mark H. Weaver's message of "Mon, 01 Jul 2019 01:06:02 -0400")
Hi again,
I wrote earlier:
> With this in mind, if SRFI-121 is to be added to Guile, it should be a
> high performance implementation. The implementation that you provided,
> which I guess is primarily taken from the sample implementation, is far
> too inefficient, at least on Guile.
I should emphasize that there's no shame in not being able to meet my
high expectations for efficiency in a SRFI-121 implementation. The code
that you provided would be quite reasonable in most contexts.
In this particular case, because of the undesirability (IMO) of
generators as an API due to their imperative nature, with their primary
justification being the efficiency they can provide, I feel justified
demanding high efficiency in this implementation. Relatively few people
would be able to meet those expectations. It requires knowledge of
Guile's implementation and compiler that relatively few people have.
With that in mind, I hope that you will not be too discouraged by this,
and that you will consider contributing to our community in the future.
Also, I will try to find the time to send a followup message with more
details on why the provided code would run inefficiently on Guile, and
how to improve it.
Best regards,
Mark
next prev parent reply other threads:[~2019-07-01 6:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 0:09 [PATCH] add SRFI: srfi-121; generators nly
2019-07-01 5:06 ` Mark H Weaver
2019-07-01 6:00 ` Mark H Weaver [this message]
2019-07-01 6:21 ` Amar Singh
-- strict thread matches above, loose matches on Subject: below --
2020-08-01 3:42 John Cowan
2020-08-02 22:39 ` Mark H Weaver
[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
2021-01-21 18:39 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
2021-04-08 15:53 ` Arthur A. Gleckler
2021-04-11 6:52 ` Linus Björnstam
2021-04-11 16:17 ` Arthur A. Gleckler
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=87woh2gupl.fsf@netris.org \
--to=mhw@netris.org \
--cc=guile-devel@gnu.org \
--cc=nly@disroot.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).