Construct EagerMacroFunction when aliasing macro function from {% from %} tag #1208
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
imported as EagerMacroFunction to avoid ClassCastException
jasmith-hs
changed the title
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.
MacroFunctions made in tags used in eager execution should be EagerMacroFunctions. This was done for those created from the
{% macro %}(EagerMacroTag) tag, but not from EagerCallTag or EagerFromTag.Specifically, there's a ClassCastException that can happen due to the assumption that in eager execution all
MacroFunctionobjects areEagerMacroFunctioninstances. This could happen when successfully importing a macro function using aFromTagwith an alias, a bug I introduced with #1117