Avoid the cost of reflection in tight loops #26
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
Thanks. Will give this a checkout on the weekend. |
rogerallen
added a commit
that referenced
this pull request
May 24, 2015
Avoid the cost of reflection in tight loops
Member
|
Thank you, Joseph. This is a nice thing to enable and be aware of. I'll look into getting rid of all the warnings as a code-cleanliness issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What?
Improve the performance of the draw fn by avoiding the cost of reflection by using type hints.
Might only be a little bump in performance but worthy of saving were possible.
I've also turned reflection warnings on, so its easier to spot reflection costs within highly repeatable code chunks.