@W-E-Brown, please attach the LaTeX source as a file to this issue. Thanks.

Or email it to me and I'll assign myself to do the work.

Editorial issue noticed:

[res.on.required] p1 is altered to say "Requires: element" instead of "Requires: paragraph" but still says "Throws: paragraph".

An added example in [structure.specification] says "an implementation-defined attribute such as [[expects]]"

Implementation-defined attributes should be scoped.

The last sentence of [structure.specifications] p4 still refers to a Postconditions: element, which should be Ensures:.

All the issues mentioned above have been fixed on the branch (as separate commits). Thanks for the quick responses, @W-E-Brown

Oops, the branch I pushed is missing all the renaming of Postconditions: to Ensures:, I forgot to merge that in before pushing it.

Instead of changing every \postconditions to \ensures throughout the library clauses, the commit I've pushed to the branch simply redefines \postconditions:

\newcommand{\postconditions}{\ensures}

So "equivalent to" doesn't propagate Requires: anymore? It seems like we should keep Requires: in [structure.specifications]/4 until we actually get rid of the element.

@jwakely: If we do get rid of an element, we should also do a global search/replace in the LaTeX, otherwise editoris will be confused for generations to come. We can do that after the mailing, though.

@timsong-cpp good point.

@jensmaurer yes, I think we should wait until all the motions are merged, then replace all \postconditions with \ensures (if we do it now we might get some creeping back in from merged motions).