add skipStringOptimizations options to toString #58
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'm optimizing the performance of a project I'm working on. It contains large paths (for example with a length of 160k). When skipping the string optimizations in toString I can see performance improvements around 7-11x. When having multiple of these large paths this adds up.
I made a simple example here: https://codepen.io/klaasvaak/pen/dyVjPje?editors=1011
Let me know if you have concerns about skipping these string optimizations.