On Thursday, 6 March 2014 at 17:16:39 UTC, knutaf wrote:
> On Thursday, 6 March 2014 at 16:58:00 UTC, Peter Alexander wrote:
>> Known issue
>>
>> https://d.puremagic.com/issues/show_bug.cgi?id=9279
>
> Thanks. Is this suggesting that if I don't use toHexString, I won't see the problem? Because if I do:
>
> auto result = sha1Of("abc");
> writefln("%s", result[0]);
>
> I still see it's showing the wrong answer (and crashes).
>
> Or is this problematic cast/construction used in other parts of the SHA1 implementation's guts?

Hmm. Looks like it's actually a separate bug then as others are suggesting. Sorry for the distraction.