Dangerous indeed /cc @mathias
-
-
The problem is that in
@nodejs we ask for the length of a string in bytes, traversing the tree, we allocate some memory with the length, and then ask to copy the string over, traversing the tree again. One traversal is totally superfluous. -
A better C++ API to do these two steps as one without double traversal will remove the need of such a trick.
- 2 more replies
New conversation -
-
-
Unfortunately not a easy problem. There is currently no good way to know upfront when to flatten. We could simply get rid of cons strings altogether, but that would just regress performance.
-
It may also fix some memory leaks. If memory serves, the rope implementation can in some edge cases cause leaks.
- 3 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.