Change where addCallToRoboInit() inserts call to $$robo$init #7793
Conversation
This file contains hidden or 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
4234b5c to
ac29a1e
Compare
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.
Change where addCallToRoboInit() inserts call to $$robo$init
addCallToRoboInit() is used to add a $$robo$init call to constructors that belong to classes that are instrumented by Jacoco (the $$robo$init method instantiates the class' shadow object). The addCallToRoboInit() method currently inserts the call to $$robo$init before the return statement. However, it is not guaranteed that a constructor will have a return statement. This change will make it so that the addCallToRoboInit() method adds the call to $$robo$init after the call to super() or this().