fix: don't rely on std.time.microTimestamp()
for accurate statistics
#8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I don't know the extent to which you care about accuracy for rendering statistics. I found when working on seamstress that the
timestamp
calls instd.time
were so unreliable as to be unusable, sometimes reporting negative time deltas within a singlefunction.
std.time.Timer
, on the other hand, has been rock-solid in my experience.