Ability to disable array content printout on UnsafeBuffer#toString(). #166
Conversation
This file contains 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
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 was a bit baffled for a few moments why IDEA didn't want to skip over a method in debug mode. It turns out the debugger calls toString() on objects quite profusely.
UnsafeBuffer#toString() if it is backed by an array will print the content of the array. For large arrays this doesn't quite work out.
I added a property so it is possible to disable the printout while maintaining backward compatibility. If it is not an issue, maybe better to just go without printing the content altogether?
Also added for ExpandableArrayBuffer.