Ensure we're not UNPROTECT()ing 'x' in gsumm #6306
Merged
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.
rchk
is still throwing issues around here:The only thing I can think of is that the
UNPROTECT()
is applying tox
, notas
:IINM that means we have to keep
as
protected as long asx
is? Or we have to clutter the code to doUNPROTECT(2)
(x
,as
), followed immediately byPROTECT(x)
to get it back under protection? Not even sure that will work, and probably not worth the clutter.