2018

• posts Dec 16 Trade Beats
• notes Oct 30 [EMCpp]Item-40 Use std::atomic for Concurrency, volatile for Special Memory
• notes Oct 11 [EMCpp]Item-39 Consider Void Futures for One-Shot Event Communication
• notes Oct 9 [EMCpp]Item-38 Be Aware of Varying Thread Handle Destructor Behavior
• notes Oct 2 [EMCpp]Item-37 Make std::threads Unjoinable on All Paths
• notes Oct 1 [EMCpp]Item-36 Specify std::launch::async if Asynchronicity Is Essential
• notes Aug 28 [EMCpp]Item-35 Prefer Task-Based Programming to Thread-Based
• notes Aug 24 [EMCpp]Item-34 Prefer Lambdas to std::bind
• notes Aug 23 [EMCpp]Item-33 Use decltype on auto&& parameters to std::forward them
• notes Aug 22 [EMCpp]Item-32 Use Init Capture to Move Objects Into Closures
• notes Aug 21 [EMCpp]Item-31 Avoid Default Capture Modes
• notes Aug 19 [EMCpp]Item-30 Failure Cases in Perfect Forwarding
• notes Aug 18 [EMCpp]Item-29 Assume Move Operations Are Not Present Not Cheap, and Not Used
• notes Aug 17 [EMCpp]Item-28 Understand Reference Collapsing
• notes Aug 15 [EMCpp]Item-27 Alternatives to Overloading on Universal References
• notes Aug 13 [EMCpp]Item-26 Avoid Overloading on Universal References
• notes Aug 11 [EMCpp]Item-25 Use std::move on Rvalue References, std::forward on Universal References
• notes Aug 8 [EMCpp]Item-24 Distinguish Universal References From Rvalue References
• notes Aug 7 [EMCpp]Item-23 Understand std::Move and std::Forward
• notes Aug 5 [EMCpp]Item-22 When Using Pimple Idiom, Define Special Member Functions in the Implementation File