return by reference of the BigInteger after copy assignment (operator =). #24
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.
I think return by reference rather then by value after assignment (operator =) is more reasonable.
return a reference can make the
struct BigInteger
more similar to the built-inint
.consider the code following:
int one;
BigInterger big_one;
(one = 1) = 2;
(big_one = 1) =2;
after assignment, both
big_one
andone
should be 2.can do this by return reference after assignment.