Add configuration option for allowing for-loops #351
Merged
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
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.
For the ISR cooperation, we promised a config-option that turns the reconstruction of for-loops on and off.
This is now implemented. If the option is set to
true, still all other configuration options have to hold in order to reconstruct a for-loop. If it is set tofalse, no for loop is restructured.Question: This overwrites the option
force_for_loop, i.e., ifrestructure_for_loopis set tofalseandforce_for_looptotrue, no for-loop is restructured. Do we want a warning in this scenario?