[Issue 13433] Request: Clock.currTime option to use CLOCK_REALTIME_COARSE / CLOCK_REALTIME_FAST

[via Digitalmars-d-bugs]

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

--- Comment #12 from Jonathan M Davis <jmdavisProg at gmx.com> ---
As I said, I'm not against adding it. It just seems to me that in most cases
where you'd be getting the time that quickly, it wouldn't make sense to only
have a resolution of 1 ms. And even if it's being filtered, I would think that
it would usually be rather ridiculous to be logging stuff hundreds of thousands
of times a second and that the number of logging statements should be seriously
reduced in such code, so I really think that that's a pretty crazy use case.
But I'll add the ability to use the coarse clock instead and let folks shoot
themselves in the foot with it if they really want to. Given that it was added
to both Linux and FreeBSD's APIs, presumably there are at least some folks who
think that it's worth having, even if I think that it's kind of crazy.

--