Bradley T. Hughes 409b3b42a2 Remove cast and assignment operators from QAtomicInt and QAtomicPointer ... This is a source incompatible change. There is concern that the convenience of the implicit cast and assignment operators can lead to misuse. Several commits have already been done that remove excess use of the implicit cast, which is a *volatile* read every time it's used. Users of the QAtomic* API should have to think about when they are loading the value, and if they do or don't need the acquire memory barrier on load. The code that people would write using this API is meant to be multi-threaded, concurrent, and correct. The API should not allow them to inadvertently, possibly unknowingly, shoot themselves in the foot. SC-break-rubber-stamped-by: Lars Knoll Change-Id: I88fbc26d9db7b5ec80a58ad6271ffa13bbfd191f Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>		2011-12-02 13:21:32 +01:00
..
.gitignore	Moving relevant tests to corelib/thread	2011-09-01 12:54:58 +02:00
qatomicpointer.pro	Cleanup corelib autotests	2011-11-11 02:45:05 +01:00
tst_qatomicpointer.cpp	Remove cast and assignment operators from QAtomicInt and QAtomicPointer	2011-12-02 13:21:32 +01:00