Dismantling requirements tables 29-36

[tkoeppe]

To convert the lib-intro requirements tables 29-36 into paragraphs, we don't currently have any section, and no good way to reference them.

Idea:

1. A new subsection "16.4.4.?: Basic type requirements", after [16.4.4.2, utility.arg.requirements] and before [16.4.4.3, swappable.requirements].
2. New nested subsections for each individual requirement, so that we can reference them individually (which is currently possible via the tables).

Thoughts?

[tkoeppe]

@jensmaurer, @jwakely feedback welcome!

[Dani-Hub]

Personally, I would strongly prefer to make each requirement individually referencable.

[tkoeppe]

@Dani-Hub Would it be sufficient to have a (very short) subsection for each requirement?

[tkoeppe]

Maybe we don't need a new grouping subsection, but instead we can just put each requirement straight into its own level-3 subsection, so we'd have new subsections 16.4.4.3 -- 16.4.4.9.

[Dani-Hub]

@Dani-Hub Would it be sufficient to have a (very short) subsection for each requirement?

Yes, sure, we don't need extraordinary overhead. It is just the thing that we want to refer to them individually.

[tkoeppe]

Note to selves: the fpos.requirements table should be quite easy to dismantle, too.

[Dani-Hub]

Note to selves: the fpos.requirements table should be quite easy to dismantle, too.

I'm eagerly awaiting that.

[tkoeppe]

@Dani-Hub PRs are of course always welcome :-)

[AlisdairM]

I will be looking into this in the New Year (2024) if no-one beats me to it. It is annoying how often these requirements tables float into misleading subsections due to page breaking.

Feel free to "assign" me the ticket so I do not forget.