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

Move semantic checks shouldn't be based on ranges #1388

Closed
sithhell opened this issue Mar 1, 2015 · 5 comments
Closed

Move semantic checks shouldn't be based on ranges #1388

sithhell opened this issue Mar 1, 2015 · 5 comments

Comments

@sithhell
Copy link
Member

sithhell commented Mar 1, 2015

Our move semantics tests should check for a fixed number of copies instead of ranges for known compilers.

@K-ballo
Copy link
Member

K-ballo commented Apr 21, 2015

It was noted that the use of void_guard inhibits elision in MSVC.

@K-ballo
Copy link
Member

K-ballo commented Apr 22, 2015

Probably wise to wait until #1474 (Remove serialize_as_future and invoke_when_ready) happens

@hkaiser hkaiser modified the milestones: 0.9.11, 0.9.12 Nov 12, 2015
@hkaiser
Copy link
Member

hkaiser commented Mar 25, 2016

FWIW, #1474 has long been closed now.

@hkaiser hkaiser modified the milestones: 0.9.99, 1.0.0 Jun 27, 2016
@hkaiser hkaiser modified the milestones: 1.0.0, 1.1.0 Apr 23, 2017
@msimberg msimberg removed this from the 1.1.0 milestone Nov 21, 2017
@stale
Copy link

stale bot commented Jul 4, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the tag: wontfix label Jul 4, 2019
@stale
Copy link

stale bot commented Aug 3, 2019

This issue has been automatically closed. Please re-open if necessary.

@stale stale bot closed this as completed Aug 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants