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

Please explicitly disable serialization in classes that don't support it #870

Closed
eschnett opened this issue Sep 23, 2013 · 2 comments

Comments

Projects
None yet
3 participants
@eschnett
Copy link
Contributor

commented Sep 23, 2013

HPX components, clients, and futures cannot be serialized -- this (seems to) lead to run-time errors. Please disable serialization there, either at compile time, or by triggering a run-time error that describes the problem.

It is quite easy to accidentally serialize such objects, e.g. if they are mentioned in an async call or are mentioned in a lambda that is part of a future. More error checking would help me here.

@sithhell

This comment has been minimized.

Copy link
Member

commented Sep 23, 2013

if you try to serialize a future or a component you will get a compile time error. The problem with clients is that they can not be serialized out of hpx threads. I will get to this problem ASAP.

@ghost ghost assigned hkaiser Sep 23, 2013

@hkaiser

This comment has been minimized.

Copy link
Member

commented Sep 23, 2013

We should remove serialization support for hpx::components::client_base<> for now. It can be re-added later once we solved the underlying issue - namely that the future stored in client_base can't be serialized on a non-HPX-thread.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.