Fix MonoTimer
and Timer::syst
frequency
#236
Merged
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.
Continuation of #191, broken into its own PR because I didn't want to force push to someone elses master branch 😉
After some correct testing, I reproduced the bug. I also noticed the same problem with
Timer::syst
using the following code:which uses the now functioning MonoTimer to measure the incorrectness of syst, which is now 4 times slower than intended.
cc: @ra-kete