Previously I wondered, from musing when reading Herb Sutter’s updated Guru of the Week 6b article, how one might – in C++11 – enforce a concurrent usage pattern in which an object can only be modified after creation by the creating thread until all modifications are done when the object becomes immutable and concurrently accessible. Concurrent access before an object becomes immutable is considered an error as are attempts to modify an object that is immutable.
Submitted by Ralph McArdell on Mon, 08 Jul 2013 15:53:13 +0100
Updated: Sat, 08 Jun 2019 10:17:14 +0100
Submitted by Ralph McArdell on Fri, 31 May 2013 16:49:05 +0100
Updated: Sat, 08 Jun 2019 10:16:15 +0100