From: Marko Rauhamaa <marko@pacujo.net>
To: Christopher Howard <christopher.howard@qlfiles.net>
Cc: Guile User Mailing List <guile-user@gnu.org>
Subject: Re: Self balancing trees
Date: Tue, 22 Aug 2017 07:31:06 +0300 [thread overview]
Message-ID: <87pobow7ed.fsf@elektro.pacujo.net> (raw)
In-Reply-To: <1503370332.914.5.camel@qlfiles.net> (Christopher Howard's message of "Mon, 21 Aug 2017 18:52:12 -0800")
Christopher Howard <christopher.howard@qlfiles.net>:
> Hello, where do I find a self-balancing tree structure to use with
> guile? I'm new to guile, but I can't seem to find what I'm looking for
> in the guile info document, or in the gnu guile library collection.
If you can't find anything else, here's mine:
http://pacujo.net/~marko/avl-tree.scm
Marko
next prev parent reply other threads:[~2017-08-22 4:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 2:52 Self balancing trees Christopher Howard
2017-08-22 4:31 ` Marko Rauhamaa [this message]
2017-08-22 5:07 ` Christopher Howard
2017-08-22 5:16 ` Marko Rauhamaa
2017-08-22 9:33 ` Kovacsics Róbert
2017-08-23 4:00 ` Nala Ginrut
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=87pobow7ed.fsf@elektro.pacujo.net \
--to=marko@pacujo.net \
--cc=christopher.howard@qlfiles.net \
--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).