[hardware.interference] prefer itemdecl to codeblock #836
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The new hardware interference constants are introduced above the definition of their semantics with a codeblock, rather than an itemdecl, macro. Prefer the latter for consistently introducing names that are about to be defined, as this will simply auditing the text in the future, e.g., when trying to reivew that every itemdecl has a corresponding library index entry.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The new hardware interference constants are introduced
above the definition of their semantics with a codeblock,
rather than an itemdecl, macro. Prefer the latter for
consistently introducing names that are about to be defined,
as this will simply auditing the text in the future, e.g.,
when trying to reivew that every itemdecl has a corresponding
library index entry.