Fix issue tracking recursive references to custom annotations #197
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.
Custom annotations (introduced in #110) allow users to define arbitrary annotations that can be used by calling an autogenerated processor for the Python backend. The Python backend code generation recursively searches for and includes custom annotation types for a backend, but the intermediate code generator does not track references recursively. This leads to missing imports in the Python code generation in some cases.
This change moves the recursive search into the intermediate code generator and puts the result in a new data type field for use in code generation by backends.
Checklist
General Contributing
Is This a Code Change?
Validation
tox
?