From: "Jéssica Milaré" <jessymilare@gmail.com>
To: guile-devel@gnu.org
Subject: Proposal of a better hash table implementation based on SRFI 125
Date: Fri, 28 Dec 2018 14:11:51 -0200 [thread overview]
Message-ID: <CAGBcF1Zs4=36KWFEEcTSfDhPpp02RYCrTYwu=JtT21a7iPXe3A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1029 bytes --]
Hello,
As I said in a previous e-mail, currently SRFI-69 is broken for weak hash
tables - and I've sent a patch to fix it. However, I think there are many
other problems with current implementation of hash tables. There are guile
standard hash tables, SRFI-69 hash tables (which is implemented on top of
standard hash tables) and also R6RS hash tables (which is implemented on
top or SRFI-69 and completely lacks support for weak keys and/or values).
I think that should be fixed and guile should have only two kinds of hash
tables: the standard guile hash table and another extended hash table type
that will be used directly by R6RS, SRFI-125 and SRFI-69. In my opinion, it
should be based on SRFI-125, which is part of R7RS Red Edition, but also
supports some other procedures to make it compatible with R6RS and SRFI-69,
supporting weakness and immutable hash tables.
I'm already implementing the SRFI-125 based hash tables library for myself,
so, if that is accepted, I can also make a patch for guile.
Regards,
Jessica
[-- Attachment #2: Type: text/html, Size: 1165 bytes --]
next reply other threads:[~2018-12-28 16:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-28 16:11 Jéssica Milaré [this message]
2018-12-30 17:50 ` Proposal of a better hash table implementation based on SRFI 125 Amirouche Boubekki
2019-01-12 20:34 ` Jéssica Milaré
2019-01-13 22:50 ` Jéssica Milaré
2019-01-16 23:38 ` Arne Babenhauserheide
2019-01-17 0:18 ` Amirouche Boubekki
2019-01-17 21:13 ` Jéssica Milaré
2019-01-17 21:14 ` Jéssica Milaré
2019-01-20 12:57 ` Amirouche Boubekki
2019-01-20 13:50 ` Jéssica Milaré
2019-01-20 18:32 ` Amirouche Boubekki
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='CAGBcF1Zs4=36KWFEEcTSfDhPpp02RYCrTYwu=JtT21a7iPXe3A@mail.gmail.com' \
--to=jessymilare@gmail.com \
--cc=guile-devel@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).