Make imap_go
eval rule lazy in index argument (copy #2543)
#2947
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.
Fixes #2542
The problem was that in the final recursive call, when
imap_go
would returnNil
, the index argument was out-of-bounds. And becauseimap_go
was strict in all arguments,imap_go
would make theNil
undefined.Subsequently applying
reverse
where theNil
is undefined, gives us a complete vector that is undefined, given thatreverse
is strict in its vector argument.Still TODO:
This is an automatic copy of pull request #2543 done by [Mergify](https://mergify.com).