public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com> To: gdr@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: libstdc++/3552: missing hash function for std::string Date: Wed, 08 May 2002 11:46:00 -0000 [thread overview] Message-ID: <20020508184602.6278.qmail@sources.redhat.com> (raw) The following reply was made to PR libstdc++/3552; it has been noted by GNATS. From: Phil Edwards <phil@jaj.com> To: Goswin Brederlow <goswin.brederlow@student.uni-tuebingen.de> Cc: Vadim Ogranovich <vograno@arbitrade.com>, "'gcc-gnats@gcc.gnu.org'" <gcc-gnats@gcc.gnu.org>, "'Laurent.Bonnaud@inpg.fr'" <Laurent.Bonnaud@inpg.fr>, "'87063-quiet@bugs.debian.org'" <87063-quiet@bugs.debian.org>, "'gcc-bugs@gcc.gnu.org'" <gcc-bugs@gcc.gnu.org> Subject: Re: libstdc++/3552: missing hash function for std::string Date: Wed, 8 May 2002 14:38:48 -0400 On Wed, May 08, 2002 at 07:01:45PM +0200, Goswin Brederlow wrote: > > Yes. How can we possibly guess what a good hash function would be for > > arbitrary strings? Efficiency of hashing is extremely dependant on the > > data being hashed. You need to write one that's appropriate for your data; > > this will involve multiple experiments. > > > > There is std::collate::hash() for char*'s, but this is essentially a > > generic guess, and should only be used when you haven't yet had the time > > to come up with a more appropriate function. > > Having one for char* but not for string is a bit of a contradiction. I'd like to remove the one for char*, actually... The implementation of hashing currently being proposed for C++0x apparently uses a completely different interface. I'd rather just improve the (eventual) standard version, rather than kicking along the extensions that we inherited. Phil -- If ye love wealth greater than liberty, the tranquility of servitude greater than the animating contest for freedom, go home and leave us in peace. We seek not your counsel, nor your arms. Crouch down and lick the hand that feeds you; and may posterity forget that ye were our countrymen. - Samuel Adams
next reply other threads:[~2002-05-08 18:46 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-08 11:46 Phil Edwards [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-05-08 10:06 Goswin Brederlow 2002-04-29 12:56 Vadim Ogranovich 2002-04-29 12:46 Phil Edwards 2002-04-29 12:16 Phil Edwards 2002-04-27 12:46 Vadim Ogranovich 2001-07-03 16:26 Gabriel Dos Reis 2001-07-03 16:18 gdr 2001-07-03 15:26 Matthias Klose
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 * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20020508184602.6278.qmail@sources.redhat.com \ --to=phil@jaj.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=gdr@gcc.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: linkBe 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).