[darcs-users] Crypto 4.2.0 and hashed-storage?
wchogg at gmail.com
Wed Feb 18 14:45:05 UTC 2009
Improving the speed of Crypto was something I was planning on working
on the future, so I'd be more than happy to take you up on your
challenge! I wouldn't be able to start any time in the next two
weeks, though, because of work related to next release of
As far as the Hackathon, I'm considering going but at the moment money
is a constraint & I need to figure out the budgeting.
On Wed, Feb 18, 2009 at 8:17 AM, Eric Kow <kowey at darcs.net> wrote:
> Hi Creighton,
> May we challenge you into making a version of Crypto that is suitable
> for use by darcs? Right now, we are using SHA1 and SHA256. I recall
> seeing some remarks about the Crypto SHA1 implementation being more
> 'functional' but slower than the darcs one...
> (any chance you'll be at the Hackathon?)
> On Wed, Feb 18, 2009 at 11:32:20 +0100, Petr Rockai wrote:
>> Eric Kow <kowey at darcs.net> writes:
>> > Should hashed-storage be making use of the Crypto library?
>> When Crypto exports a fast bytestring-lazy interface, sure. Unfortunately, that
>> is not the case, it currently uses lists and converting to lists for computing
>> digests is not quite feasible. I'd be happy to use it though, if this is
>> addressed... (and, well, if the sha256 performance is reasonably close to the C
>> implementation I lifted from darcs, but I don't expect this to be much of a
> Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow>
> PGP Key ID: 08AC04F9
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> -----END PGP SIGNATURE-----
More information about the darcs-users