Add API to provide file name for parse_tree#21
Merged
igaray merged 1 commit intoinaka:masterfrom Nov 1, 2017
Merged
Conversation
aleppo does better job when it knows file name (eg, '?FILE' macro and relative includes)
Contributor
|
LGTM |
Member
|
LCTM, @jfacorro :P Also, LGTM. |
igaray
approved these changes
Oct 31, 2017
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
3 participants
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.
aleppo does better job when it knows file name (eg, '?FILE' macro and
relative includes)
This one intended to be used with inaka/aleppo#46, so, if that one will be merged and new tag will be pushed, it would be nice to upgrade
aleppodependency as well.