Skip to content

Conversation

@GeertvanHorrik
Copy link
Member

This PR uses Stopwatch.GetTimestamp instead of creating a new stopwatch which results in both memory and performance improvements.

Fixes #575

Image

Copy link
Member

@ltrzesniewski ltrzesniewski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍

  • I cleaned up some stuff while reviewing
  • The readme would need an update after this change

@GeertvanHorrik
Copy link
Member Author

Beautiful cleanup, thank you. I started working on the nullable things, but didn't want to mix it into this PR, but will do it in a next PR.

Also updated the readme.

@SimonCropp
Copy link
Member

lgtm. want me to deploy?

@GeertvanHorrik
Copy link
Member Author

lgtm. want me to deploy?

yes please, thank you! I will create another PR after the release to introduce nullable.

@SimonCropp SimonCropp added this to the 3.2.3 milestone Feb 24, 2025
@SimonCropp SimonCropp merged commit 90b48a5 into master Feb 24, 2025
3 checks passed
@SimonCropp SimonCropp deleted the feature/struct-stopwatch-take-2 branch February 24, 2025 11:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Consider using ValueStopWatch

4 participants