Fix annotation-related compiler assertion failure (issue #1751) #1757
Conversation
This file contains 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
Fixes #1751, a compiler assertion error related to this system.
jemc
force-pushed
the
fix/annotation-type-assert
branch
from
c28dd31
to
55b0f32
Compare
jemc
added
the
changelog - fixed
jemc
changed the title
jemc
changed the title
jemc
changed the title
jemc
changed the title
Praetonus
approved these changes
Mar 27, 2017
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.
This PR fixes #1751, a compiler assertion error related to the efficient storage system for AST annotations and types, introduced in #1649.
This PR also changes the system somewhat, to rely on the token type that annotations use (
TK_BACKSLASH), instead of using theAST_ANNOTATEDflag.