This repository has been archived by the owner on Jun 20, 2019. It is now read-only.
Only call class invariant if one provably exists in any base classes #132
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.
This is an interesting optimization that turns:
Into:
If the given
MyClass
object has no invariants found in it's vtable.In some contrived benchmarks, I found this to achieve 2% better runtime results in non-release builds vs. turning off invariants altogether with
-fno-invariants
(with-O2
, I should try non-optimized builds too).Just waiting to here back if there are any thoughts in the community on this, but I can't think of a problem on my end.