Fix #62: Do not tag some classes as storage keywords #63
Conversation
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
|
@nicolasstucki The CI is not happy. |
nicolasstucki
force-pushed
the
fix-#62
branch
from
3ea7f7d to
c4785ce
Compare
|
@liufengyun CI passes now |
Do coloring Unit, Boolean, Byte, Char, Short, Int, Float, Long, Double, String, Nil, None, Symbol and self with colors that do not represent their semantics.
|
Squashed and rebased |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Avoid coloring
Unit,Boolean,Byte,Char,Short,Int,Float,Long,Double,StringandSymbolas keywords. Use the same color for all types and companion object references.Note that keyworks are in blue and types are in green(ish).
Old
With this PR
