Skip to content

[sysvabi64] Define a mechanism to separate requirements from guidance/explanation #367

@smithp35

Description

@smithp35

The sysvabi64 document has a mixture of requirement, such as the size limits for the code-models, and guidance such as example PLT sequences. One of the most common flavour of review comments is interpreting guidance as a requirement.

We would like to define a mechanism, such as moving the guidance to an appendix, or just locally highlighting a section as guidance so we can make it easier to enumerate the requirements.

This issue is to capture any discussion about the mechanism. PRs can then be raised to implement.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions