From: Daniel Hartwig <mandyke@gmail.com>
To: "Taylan Ulrich B." <taylanbayirli@gmail.com>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: guile-json 0.2.0 released
Date: Fri, 5 Apr 2013 07:39:29 +0800 [thread overview]
Message-ID: <CAN3veRfomBqTappYNC7NYg6=cO3goEbAepeM+fca8adSRbQH9Q@mail.gmail.com> (raw)
In-Reply-To: <8738v63pj4.fsf@taylan.dyndns.org>
On 5 April 2013 06:21, Taylan Ulrich B. <taylanbayirli@gmail.com> wrote:
> Panicz Maciej Godek <godek.maciek@gmail.com> writes:
>
>> Plainly, the size is kept in the internal representation of the hash
>> table:
>>
>> typedef struct scm_t_hashtable {
>> unsigned long n_items; /* number of items in table */
>> ...
>>
>> cf.
>> http://git.savannah.gnu.org/gitweb/?p=guile.git;a=blob;f=libguile/hashtab.
>> h;h=82ed22e66eb1f5045793cfc55cca0be040d4aab1;hb=HEAD#l66
>>
>> It would be really cheap&easy to get it from there. I just wanted to
>> show that hash-tables are neglected in Scheme in general, and in Guile
>> in particular.
>
> That sounds nasty indeed. It's late for me today; if no one's quicker
> than me, tomorrow I might see that I implement hash-size in C as my
> first Guile-contribution. :P
>
Note that exposing a constant-time “number of items” operation has been
proposed several times recently and remains not included. Please read
the previous threads before proposing this yet again.
Regards
next prev parent reply other threads:[~2013-04-04 23:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 7:08 guile-json 0.2.0 released Aleix Conchillo Flaqué
2013-04-04 9:11 ` Panicz Maciej Godek
2013-04-04 10:15 ` Taylan Ulrich B.
2013-04-04 12:06 ` Panicz Maciej Godek
2013-04-04 22:21 ` Taylan Ulrich B.
2013-04-04 22:59 ` Aleix Conchillo Flaqué
2013-04-05 7:35 ` Panicz Maciej Godek
2013-04-04 23:39 ` Daniel Hartwig [this message]
2013-04-07 11:40 ` Panicz Maciej Godek
2013-04-07 20:38 ` Taylan Ulrich B.
2013-04-08 1:51 ` Daniel Hartwig
2013-04-08 2:11 ` Daniel Hartwig
2013-04-05 0:17 ` Daniel Hartwig
2013-04-05 2:47 ` Noah Lavine
2013-04-05 9:35 ` Daniel Hartwig
2013-04-05 13:18 ` Noah Lavine
2013-04-05 9:41 ` Panicz Maciej Godek
[not found] ` <CAPjoZodAaHLfPGb+XiUhoMJD7J4_kYrjRmYP+p1S5w5yuPgLEg@mail.gmail.com>
[not found] ` <CAPjoZoc12W4usGnkwSZG2zNqe8xF6C4hWWZgq+-Nc8HMg_Xw4Q@mail.gmail.com>
2013-04-04 15:11 ` 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='CAN3veRfomBqTappYNC7NYg6=cO3goEbAepeM+fca8adSRbQH9Q@mail.gmail.com' \
--to=mandyke@gmail.com \
--cc=guile-user@gnu.org \
--cc=taylanbayirli@gmail.com \
/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).