Add object length limit #778
Merged
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.
What problem did you solve?
Closes #174
This PR introduces a new setting
r.session.objectLengthLimitcorresponding to R optionvsc.object_length_limitto limit the length of objects to provide names in session symbol completion, hover, and workspace viewer item.Then large named objects with many elements will not be called
names(). The overhead of callingnames()(on environment) and writing the names toglobalenv.jsonshould be reduced.(If you do not have screenshot) How can I check this pull request?
For the following code, before this PR, the delay will be more and more significant if more objects with many elements are created in the global environment.
With this PR being effective, creating
lst2andlst3should no longer cause a permanent delay on all subsequent calculations. One should also observe that the auto-completion works withlst1but notlst2orlst3due to object length limit, and the workspace viewer item oflst1should show object details whilelst2andlst3do not ifr.session.levelOfObjectDetailis set toDetailed. Adjustingr.session.objectLengthLimitshould work accordingly.