[Issue 12886] std.datetime cannot parse HTTP date

[via Digitalmars-d-bugs]

https://issues.dlang.org/show_bug.cgi?id=12886

--- Comment #3 from Jonathan M Davis <jmdavisProg at gmx.com> ---
Well, I can certainly do it, though I wouldn't make it as flexible as what I'm
doing for the library that I'm working on. Supporting CFWS (comment folding
whitespace) will certainly make it worse, but that would be hidden from the
API. It just makes for some ugly code.

Would supporting random-access ranges of char and ubyte (as well as string) be
sufficient? Adding more than that pretty much means duplicating all of the
code, which I don't like (much as I'm going to do it in my library for
flexibility's sake), and given where these dates are _supposed_ to be used, it
doesn't necessarily make sense to support wchar[] or dchar[]. Or I could just
make it operate on ranges of dchar and not care much about efficiency, though
I'm not a fan of that idea. What I've been working on is specifically written
with the idea that you're operating on ranges of char or ubyte, because that's
what IMF (rfc 5322) messages always are.

--