Fix two issues with ast.to_lua_source()#45
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
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 pull request is fixing two issues I've been encountering while using
ast.to_lua_source()and for which you have issues opened:return Falseinstead ofreturnto_lua_source issue when returning empty value #44local some_var =instead oflocal some_varAST deserialization (to_lua_source) issue with assign's that have no values #37I'm not sure if my patch is the good way to do it, but at least I tested it and it's working as expected.
Please let me know if I should change anything to get my pull-request accepted.