Simon Brown@sjb3dFixing a data race by locally copying const data to allow side-effects (on copy), reminded of this C++ talk:herbsutter.comVideo: You Don’t Know const and mutableAt C++ and Beyond in August, I gave a 30 min talk on the changed meaning of const and mutable. The talk video is now online: You Don’t Know [keyword] and [keyword] const means const. Bonus: mutable…1:22 PM · Mar 25, 2013·Twitter Web Client4 Likes
(BLM) Sean Barrett@nothings·Mar 25, 2013Replying to @sjb3d@sjb3d I don't follow the logic in that talk; seems like funcs called from lib forbidden to *modify*, not forbidden to thread-unsafe-modify.1
Simon Brown@sjb3d·Mar 26, 2013Replying to @nothings@nothings I think Herb is arguing that means *logically modify* (i.e. non-const ops), i.e. stdlib objects guarantee const implies threadsafe1
(BLM) Sean Barrett@nothings·Mar 25, 2013Replying to @sjb3d@sjb3d (I.e. basically Andy Prowl's comment on http://isocpp.org/blog/2012/12/you-dont-know-const-and-mutable-herb-sutter… )
