Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't delete copy constructor when rvalue references are disabled #3

Merged
merged 1 commit into from
Sep 23, 2014

Conversation

MarcelRaad
Copy link
Contributor

Before SVN r82706 from February 2013 (git a7091d1), Boost.Move worked perfectly for compilers that supported deleted functions without supporting rvalue references (for example, clang with libstdc++ 4.2.1 on Mac to support OS X 10.6). r82706 broke those setups as temporaries now call the deleted copy constructor instead of the move constructor. This change reverts those setups to the old behavior.

Before SVN r82706 from February 2013 (git a7091d1), Boost.Move worked perfectly for compilers that supported deleted functions without supporting rvalue references (for example, clang with libstdc++ 4.2.1 on Mac to support OS X 10.6). r82706 broke those setups as temporaries now call the deleted copy constructor instead of the move constructor. This change reverts those setups to the old behavior.
@igaztanaga igaztanaga merged commit 9f31553 into boostorg:develop Sep 23, 2014
igaztanaga added a commit that referenced this pull request Sep 23, 2014
@igaztanaga
Copy link
Member

Thanks for the patch!

@MarcelRaad MarcelRaad deleted the patch-1 branch September 23, 2014 14:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants