CppCon 2017: Ansel Sermersheim “Multithreading is the answer. What is the question? (part 2 of 2)”

[@ChristianBrugger]

The first part of this talk is outstanding. I think the second part falls a bit into the trap of "here is all there is in this one library" instead of motivating problems and developing generic solutions more gradually, as the first part so nicely did. However this part of the talk is a very good example of what Sean Perant means by "no raw synchronization primitives".

[@williamchamberlain2263]

Great talk. Interesting theory, interesting implementation. Who's the guy at 42:00 - I'd like to see his talk, if it's on video.

[@echosystemd]

I think it's Fedor Pikus. You can search his name + "cppcon".

[@andmefikri7555]

RCU madness!

[@hmpcon]

Good talk. I really liked the examples, but I got the sense that some of the examples he gave for why this was a better solution felt like workarounds to a set of badly designed components. Eg. saying the mutable lock + const method doesn't work in the general case where you have different objects being const at different times seems like a design flaw. The latter shouldn't really happen if you have well-designed compoenents each responsible for one thing.

[@iyalovecky]

I like question for const modifier on lookup and the answer isn't satisfiable for me. But in general this talk is good.

[@tetramaximum]

I guess, at about 11:40 the return statement should use the "patronTicket", otherwise it looks like a typo.

[@greenfloatingtoad]

This reminds me of the way clojure handles mutation

[@Kodreanu23]

Great talk, great ideas... Big thanks!