[utility.arg.requirements] reformat in a style like [container.reqmts]

[notdanhan]

It looks like this now

Additional work was needed to change some \tref{} to \iref{} across the document, along with two reflows of paragraphs to stop hbox badness

I did some mild rewording in source/lib-intro.tex to make it make sense in the new format. I hope to have not introduced any wording defects! :)

[frederick-vs-ja]

Do we need to say decltype(expr) in Result? I think Result is already specifying the result type and value category of the expression in decltype-style.

[notdanhan]

I'm actually not sure, should I just keep the exposition concept here?

[tkoeppe]

This is awesome, thank you very much, @notdanhan!

[tkoeppe]

@notdanhan do also feel free to sqash, rebase and force-submit at some point. Having the full edit history isn't so important at this point.

[notdanhan]

Notes:
In order to prevent hbox badness caused by \iref for very long clause names, I reordered Cpp17Requirements in the same paragraph, I'd assume this would not change the semantic requirements but if that's a no-no I will return them to their former order

[notdanhan]

this was moved to the end to stop hbox badness

[jwakely]

I think it makes more sense in the original order, construction, assignment, swap.

Have you tried putting hyphenation hints instead, e.g. Default\-Construct\-ible and Copy\-Assign\-able and Swapp\-able?

[notdanhan]

Swappable and EqualityComparable were swapped to avoid hbox badness

[jwakely]

Again, I prefer the original order if it's possible to preserve it with hyphenation hints.

[notdanhan]

I tried adding them and PdfLatex wouldn't take the bait, no matter what I tried, so I had to reorder :( I could add forced line breaks if needs be.

…

On Mon 21 Sept 2026, 14:04 Jonathan Wakely, ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In source/utilities.tex <#9142 (comment)>: > the \oldconcept{Swappable} requirements\iref{swappable.requirements}, +the \oldconcept{CopyAssignable} requirements~\iref{cpp17.copyassignable}, I think it makes more sense in the original order, construction, assignment, swap. Have you tried putting hyphenation hints instead, e.g. Default-Construct-ible and Copy-Assign-able and Swapp-able? — Reply to this email directly, view it on GitHub <#9142?email_source=notifications&email_token=AC72MTZCXPUNALUMI35K4KD5QERORA5CNFSNUABKM5UWIORPF5TWS5BNNB2WEL2QOVWGYUTFOF2WK43UKJSXM2LFO4XTKMRWGY4TCNJWGI4KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#discussion_r4062364572>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC72MT4JYXUCRDIWVOHYPYT5QERORAVCNFSNUABDKJSXA33TNF2G64TZHMZDEMJWGI2DSO2JONZXKZJ3GQ3DOOBXGY3TQNRQUF3AE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[jensmaurer]

Yes, we should make every effort to keep the original order. Hm... This is the first time this appears. Strange.