Fragment syntax #248
Merged
Fragment syntax #248
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
Common Lisp–style escapes.
with doubled (Smalltalk-style) escapes and no newlines.
|| tokens are now called "fragments". Primer considers strings, symbols/control words to be special cases of fragments with shorthand.
|
Docs are not as consistent as I would like, but at least the Primer explains it. I need to sync this up. I'll probably rewrite the docs in one shot once I'm done with the planned changes. |
Merged
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.
Resolves #209.
Adds the
||-delimited "fragment" tokens.|is no longer allowed unescaped in symbols, sorry, but Common Lisp has the same problem, and it is a design goal of Hissp to be mostly compatible with Lisp editors.They currently don't allow newlines, which reduces (but does not eliminate) the problem with Parinfer. An internal
;character is still a serious problem. oakmac/parinfer#16 You should be able to inject a string instead as a workaround. Brackets might also be an issue but should be fine as long as they're paired. I think.Eliminates the
#""/""distinction.""are no longer raw. Use quoted fragments or comment strings instead.I think this will make Lissp easier to understand overall, because it's closer to how the underlying Hissp works. But I still need to rewrite a lot of docs.