More distinctions between asm blocks and assembly code #1
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.
I reviewed the entire chapter, and added some more disambiguations in cases of possible ambiguity between the entire
asm!block (includinglabelblocks) and the assembly code within it.The second commit, which I've kept separate, attempts to clarify an interaction between
noreturnandlabelblocks; however, for that commit I could use some confirmation on accuracy. The phrasing as previously written said that "Anoreturnasm block behaves just like a function which doesn't return", but that isn't accurate in the presence oflabelblocks, since the asm block can return, from thelabelblocks. I changed it to apply to "Anoreturnasm block with nolabelblocks". However, this assumes there are not more semantic connotations ofnoreturnhere that do apply to asm blocks withlabelblocks.