Bugfix/issue 20 allow non copyable non movable return types #21
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
burnpanck
force-pushed
the
bugfix/issue-20-allow-non-copyable-non-movable-return-types
branch
5 times, most recently
from
65772fb to
3a05a68
Compare
burnpanck
force-pushed
the
bugfix/issue-20-allow-non-copyable-non-movable-return-types
branch
from
3a05a68 to
7301695
Compare
|
Sorry for all the force-pushing, took me quite a few iterations until I got that AppVeyor test to actually fail! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 should fix issue #20, by allowing functions that either return a convertible return type or the exact same return type (where mandatory move/copy ellision will kick in).