P0019 : 2018-06-Rapperswil LWG review

• wording error static constexpr size_t is_always_lockfree; type should be bool
• change paragraph tag for lifefime from (6.8) to [basic.life]
• formatting: html has several function clauses (requires, effects) on the same line as function identifier, also need to match . usage with atomic versions
• concern with separate sharded lock table; Billy O'Neal implementation in Windows cannot use sharded lock table
• required_alignment note, eliminate may and refer to hardware
• constructor requires use term shall for required_alignment
• constructor lifetime requires in remark, move to requires clause following synopsis and use *ptr to name the referenced object
• constructor note, eliminate may , use could
• copy constructor can be noexcept
• load wording missing return type
• the value referenced by *ptr
• exchange wording needs return type
• exchange wording remove note because it refers to a deleted example
• add drafting note to editor regarding alignment / duplication with atomic wording
• specializations for integer, floating point, and pointer need to copy front matter from atomic

Locate the HTML for the P0019 2018-06 Rapperswil LWG review and read the checklist alongside the atomic wording it references. Work through the wording, formatting, alignment, constructor, exception, and specialization items; done means every checklist item is resolved in the updated document.