> > > Actually, it seems, that hrtime doesn't let you access the current
> > > value, which is, well, quite a major use case, isn't it?
> > Yes, that seemed weird to me, too. Did we miss anything, Anatol?
> Yeah, I thought I did that already, but well ... The ext was more about
> performance testing, at the start at least. I made some refactoring to it
> yesterday, so it is now possible to implement an arbitrary userspace timer
> using the HRTime\PerformanceCounter class. Maybe should add also
> HRTime\Timer, but it should first get a thought about some good API
> The portable parts are bundled files timer.[h|c] in the hrtime repo,
> supporting POSIX, Windows and Mac. They can be reused, or taken as an
> example, for sure.
Do you think we should merge hrtime into core or add a simple function just
like microtime() to ext/standard?