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

Adapt new meanings of 'const' and 'mutable' #664

Closed
sithhell opened this issue Jan 11, 2013 · 3 comments

Comments

Projects
None yet
2 participants
@sithhell
Copy link
Member

commented Jan 11, 2013

According to Herb Sutter 'const' and 'mutable' mean thread safe according to the new standard.
I think we should adapt this definition in the HPX code base to better document thread safety or unsafety.
A better explanation of the topic can be seen here: http://channel9.msdn.com/posts/C-and-Beyond-2012-Herb-Sutter-You-dont-know-blank-and-blank

@hkaiser

This comment has been minimized.

Copy link
Member

commented Jan 11, 2013

What did you have in mind concretely? Do you have any particular member variables in mind which need to be 'annotated'?

@sithhell

This comment has been minimized.

Copy link
Member Author

commented Jan 11, 2013

I'd say everything. As much as "logical" const-correctness affected code that wasn't const-correct. I suspect that this new definition has similar impact on existing code (Though probably not as much).

@sithhell

This comment has been minimized.

Copy link
Member Author

commented Feb 1, 2013

I think we can close this. Upon closer inspection, we already conform to those new definitions. Reopen if you feel otherwise.

@sithhell sithhell closed this Feb 1, 2013

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.