Add return statements in noreturn functions
#129
Merged
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.
(Option to) add always add return statements in functions that fall through, specifically those marked
noreturn. The justification for adding this change to CIL: currently CIL always adds a return statement if it is at all possible for the function to reach the end of its body. Fornoreturnfunctions, however, it trusts that these functions never reach their end. This makes the behaviour arguably more consistent between functions markednoreturnand functions that are not.Fixes goblint/analyzer#951. Fixes the issue blocking goblint/analyzer#953. See also goblint/analyzer#953 (comment).