Repository navigation
Explain a batch of syntax errors - #9
Merged
Merged
Conversation
if with do, a keyword as a function name, a match without do or end, an unclosed parameter list or map, a Ruby => in a map, two expressions in one ${...}, &name in place of ~name, a one-letter variable or type name, and a let with no value. Every example was checked with kex built from main.
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.
Twelve more explanations under
codes/, all parse errors.if cond do, where a blockifhas nodobreak, used as a function namematch nwithoutdomatchleft without itsend)=>in a map entry}${...}&doublein place of~doublelet total: Integerwith no valueEach broken example gives the output shown with kex built from main (371bbdff), and each fix compiles and runs.