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
Allow for default constructed parcel instances to be moved #1792
Conversation
The asserts were put in for sanity checks. A parcel without an action doesn't make a lot of sense. There might be more behind #1790, removing those asserts might just cover them up |
We move default constructed parcels, for those these asserts will fire. |
It would make more sense to check for an action only if we access it in order to invoke it, instead. |
Am 09.10.2015 1:41 vorm. schrieb "Hartmut Kaiser" <notifications@github.com
Can you show me where this is happening? I find it highly suspicious that |
Am 09.10.2015 1:42 vorm. schrieb "Hartmut Kaiser" <notifications@github.com
Why? This catches a potential error as early as possible, checking on each |
Let's add a proper check whether the parcel is valid, instead. Just the absence of a valid action does not tell anything. |
We do that in several places, for instance here. |
The callback takes the parcel by reference, no? |
That's done already here. |
The latest commit adds more comprehensive sanity checking to parcels not relying on the action only. |
LGTM, thanks! |
Allow for default constructed parcel instances to be moved
This fixes #1790: assertion 'action_.get()' failed: HPX(assertion_failure) when running Octotiger with pull request 1786