j auto-naming might delete an explicit NULL#4063
Merged
Conversation
Codecov Report
@@ Coverage Diff @@
## master #4063 +/- ##
=========================================
+ Coverage 99.4% 99.4% +<.01%
=========================================
Files 72 72
Lines 13674 13675 +1
=========================================
+ Hits 13593 13594 +1
Misses 81 81
Continue to review full report at Codecov.
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Closes #4061
explicit NULL was leading essentially to:
and then the problem.
This issue was already handled in the
ifbranch -- skip assignment if the object isNULL.