Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Editorial pass #521

Merged
merged 14 commits into from
Nov 2, 2024
Merged

Editorial pass #521

merged 14 commits into from
Nov 2, 2024

Conversation

divergentdave
Copy link
Collaborator

This rolls up a bunch of editorial changes, clarifications, and rephrasings from my pass over the document. I split it out into several topical commits, plus a couple omnibus commits of more minor changes.

Copy link
Collaborator

@cjpatton cjpatton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Excellent. I think the only thing I slightly disagree with is MAY versus SHOULD for the the none-affineness of the gadget, given the semantics of SHOULD in RFCs. But I agree that it would be silly for this to be non-affine.

@cjpatton cjpatton merged commit d007a4e into main Nov 2, 2024
6 checks passed
@divergentdave
Copy link
Collaborator Author

Yeah, looking at RFC 2119, maybe this ought to be a lower-case "should". There's no valid reason for an affine gadget, but also an affine gadget wouldn't break anything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants