unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Ian Price <ianprice90@googlemail.com>
To: Dmitry Bogatov <KAction@gnu.org>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: Uniq list in Guile
Date: Sat, 26 Oct 2013 11:16:15 +0100	[thread overview]
Message-ID: <87vc0kbamo.fsf@Kagami.home> (raw)
In-Reply-To: <87d2mspkt3.fsf@gnu.org> (Dmitry Bogatov's message of "Sat, 26 Oct 2013 11:12:40 +0400")

Dmitry Bogatov <KAction@gnu.org> writes:

> Hello!
>
> Recently I faced neseserity to uniq list in Guile. Surprised, that I
> did not found ready solution, I decided to prepare it.
It's not really that common. I wrote my own "uniq" (which is a terrible
name unix has inflicted on us) a long while back, and I think I've used
it exactly once. By contrast, I use shuffle (also not in the standard
library) fairly often, and I got that one shot down.

> By analogy with sorting functions in `sort.c` I prepared
> `uniq.c`(attached, but unfinished patch, lacking proper documentation).
> But after I became curious, how slower would be Scheme version with
> (set-cdr!). To my test (random list of small integers) it is about twice
> as slow.
>
> Is Guile Mainline interested in these routines, and if yes, does in your
> opinion doubling execution speed worth resorting to C hacking?
Without an actual benchmark, no.

-- 
Ian Price -- shift-reset.com

"Programming is like pinball. The reward for doing it well is
the opportunity to do it again" - from "The Wizardy Compiled"



  parent reply	other threads:[~2013-10-26 10:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-26  7:12 Uniq list in Guile Dmitry Bogatov
2013-10-26  8:03 ` Panicz Maciej Godek
2013-10-26  9:06   ` Thien-Thi Nguyen
2013-10-26 12:05     ` Dmitry Bogatov
2013-10-26 10:16 ` Ian Price [this message]
2013-10-26 23:14   ` 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=87vc0kbamo.fsf@Kagami.home \
    --to=ianprice90@googlemail.com \
    --cc=KAction@gnu.org \
    --cc=guile-user@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).