Use pointers instead of objects to avoid copying of significant size memory pieces#4
Open
PROger4ever wants to merge 1 commit into
Conversation
PROger4ever
force-pushed
the
PR/4_Use_pointers_instead_of_objects
branch
from
d2052b8 to
666917d
Compare
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
1 participant
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.
Introduction
Previous implementation of Varcaser uses objects instead of pointers. It makes program to copy non-small objects every time any method is called. For example, Caser objects include ~9 fields in depth to copy always.
Problem
It is a lot of wasting time to copy objects.
Solution
Use pointer like in the PR :)
Notes
The solution can be incompatible with previous code-usages.