More documentation for language definitons#3427
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
I rewrote the Language Definition section of our website. I generally expanded upon existing topics, added and simplified examples, and added some new sections.
The new sections are about token names and Prism's matching algorithm. The former explains what token names are, how they affect the color of tokens, and a what granular highlighting is. The latter explains the difference between Prism default matching mode (which I dubbed first-come, first-served (FCFS) matching), and greedy matching using examples.
While the contents should be correct, I'm not so certain about the language. I would very much appreciate someone prove reading this.