-
Notifications
You must be signed in to change notification settings - Fork 139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bare string concatenation uses lots o' stack #1795
Comments
Yup! That's still on my list. This would be fixed by #1479. If it's alright, I'm going to close this one in favor of that one. |
@kddnewton hah. I forgot I opened that or I would have added this as a comment to it. I guess the only value of opening this was to point out a real-world problem with the current implementation. |
We can also change the format of |
Thank you @duerst that's very kind. I think we should fix it on our end, however, as I'm sure it's not just that file that has this issue and we want to be as performant as possible regardless of the source. |
When JRuby is loading the serialized blob via Ruby stdlib
unicode_normalize/tables.rb
it hits large chains of strings built using string syntax concat chains:This leads to a large amount of a stack trace like:
If I increase our stack (which thankfully is possible to do with the JVM) then I can get this file to load. In legacy parsers this is all built up into a single string instead of putting it into a cons chain in the AST. JRuby does not want to grow stack to load this data file so I am wondering if we should rethink putting this into the tree or not?
The text was updated successfully, but these errors were encountered: