fix issue #1686 (jmeClone() return types) #1695
Closed
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
|
Also, I think applications should not be calling jmeClone() directly. It should only be called by JmeCloner. Perhaps leaving these as Object will help discourage users from messing up? ...and JmeCloner does not care what the method returns and so Object is fine. |
|
After thinking about this some more, I'm convinced this isn't a worthwhile change. |
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.
This is riskier than #1683. For one thing, it affects many commonly extended classes including
BetterCharacterControlandAbstractControl. Also, it modifies theJmeCloneableinterface itself.