Small fix for opAssign(T) #724
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
This either: *Asserts if autoInit==No and not initialized (instead of doing an access violation) *EnsuresInitialized if autoInit==Yes Uses "move(a, b)" instead of "b = move(a)" for slightly increased performance
|
thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Just a quick patch for opAssign(T)
This either:
*Asserts not initialized and autoInit==No (instead of doing an straight up access violation)
*calls "ensuresInitialized" if autoInit==Yes (making it work, instead of doing an access violation)
Uses "move(a, b)" instead of "b = move(a)" for slightly increased performance
Contains a stupid and small unittest, but covers as-of-yet uncovered basic usage