Repository navigation
Refactor in-range to in-inclusive-range when possible - #376
Draft
jackfirth wants to merge 1 commit into
Draft
jackfirth wants to merge 1 commit into
jackfirth wants to merge 1 commit into
Conversation
Copy link
Copy Markdown
Owner
Sorry, something went wrong.
This file contains hidden or 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
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.
Closes #153 and closes #369.
I'm keeping this open as a draft for now. It relies on a patch to Racket to emit a 'disappeared-visit syntax property. I'm not sure yet if this will work for uses of in-range in for at higher phases.