Conversation
Closed
Contributor
Contributor
|
It works well as On the other hand It generates |
Collaborator
Author
Thanks for reporting this. It's messy to solve at the moment but should be easier after an in-progress refactor so I'll leave as is for now. I added an expected failure test to track this for now. |
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.
This PR provides a mechanism for pseudo ops to be supported in Tealish. So far only
methodis added.I'll repeat a comment from the code here:
In Teal this is written as
No quotes! I'm not sure we'll ever support those directly as making the parser accept unquoted strings seems like a messy thing to do. We may just add some explicit helper functions to Tealish for these if necessary.
So in summary the only supported pseudo-op will be
methodfor now.