Concurrency TS2 (draft in wg21.link/n4895): • hazard_pointer_clean_up • Feedback welcome • Proposal for C++26: Minimal useful subset of TS2. • Why minimal? High confidence in proposal. Require less committee committee time. • Cohorts: • High confidence in usefulness based on Folly experience. • Why not C++26? Maybe. But unlikely. Complex wording takes committee time. • Global cleanup? • As in TS2? Depends on TS2 feedback • Other extensions: • Quasi-synchronous on-demand asynchronous reclamation? Minimal Proposal for C++26 Hazard Pointer Synchronous Reclamation Beyond Concurrency TS2 – Maged Michael class hazard_pointer_obj_base