Adding opAssign tests for all three runtimes #21
Conversation
This file contains 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
Emmankoko
force-pushed
the
list/opAssign
branch
from
95f72f8 to
33ddb36
Compare
|
Looks like this still need some work. Anything I can help with ? |
…on mac destory, emplace new object in address, return
Emmankoko
force-pushed
the
list/opAssign
branch
from
b73dca4 to
e55f8d3
Compare
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.
opAssign function was not available for linking on macOS. but available for the other runtimes. so the approach here is to destroy the current list object(this), emplace the new object in the current object's(this) address, and return it.