Clean up after Racket's qq-and-or.rkt -> core-syntax.rkt file rename#1510
Open
jesboat wants to merge 1 commit into
Open
Clean up after Racket's qq-and-or.rkt -> core-syntax.rkt file rename#1510jesboat wants to merge 1 commit into
jesboat wants to merge 1 commit into
Conversation
Typed Racket needed to be updated to support the file rename. We introduced a hack in the previous commit (1308803) to be compatible with the old filename and the new filename. At this point, we can reasonably assume anybody building with TR trunk is building with a Racket checkout which is post-rename, so remove the hack.
There was a problem hiding this comment.
Resyntax analyzed 1 file in this pull request and found no issues.
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.
Typed Racket needed to be updated to support the file rename. We introduced a hack in the previous commit (1308803) to be compatible with the old filename and the new filename.
At this point, we can reasonably assume anybody building with TR trunk is building with a Racket checkout which is post-rename, so remove the hack.