-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recursive inlining via InlineTransform and associated fixes #205
Merged
Merged
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
aa6c5be
TransformInline: Add option to remove unused imports to pragma inliner
mlange05 bc9d112
TransformInline: Add InlineTransformation for batch processing
mlange05 dc910e1
Loki-transform: Perform source inlining via new InlineTransformation
mlange05 aa57690
InlineTransform: Resolve associations and skip unattached calls
mlange05 f873719
TransformInline: Also remove interface header imports
mlange05 655ee8f
TransformInline: Fix elemental function inlining
mlange05 61dca1d
SanitiseTransform: Create "housekeeping" transformation for scheduler
mlange05 00a462d
SCC: Fix SCC + sequence-assoc + internal-inlining test
mlange05 be9520a
OFP: Disable OFP for regression tests
mlange05 038162d
TransformInline: Fix docstrings and add cross-linkage
mlange05 d6ba0b8
InlineElementals: Remove redundant check for .type in import symbols
mlange05 5705036
TransformSanitise: Merge tests for sanitise transformation
mlange05 63a4434
TransformSanitise: Add small test for Transformation class
mlange05 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
This file was deleted.
Oops, something went wrong.
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Conceptual question, not necessary to act upon here: Going forward, should we try to include debug output (or a new "optimisation report"-like output stream) in situations like this, where a transformation is not applied because an assumption isn't met (here: missing enrichment information).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I'm planning an overhaul of the logging from transformations once the configuration changes are more complete (so we can select log-leve per trafo, etc.).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Possibly worth capturing via an issue?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#220