-
-
Notifications
You must be signed in to change notification settings - Fork 925
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
The & operator doesn't work with quoted symbols #5066
Comments
Oh I tried searching before but now just found #3880 and related and this is probably the same |
The workaround seems to be saving the quoted symbol to a variable and calling with that (which maybe suggests it's not an encoding issue) |
fwiw bytelist_love branch does work now but I also find this super weird that it is broken. It is already ascii and a symbol. Even with utf-8 as default this encoding should be US-ASCII. |
We were building a String with the entire bytelist buffer for symbols instead of proper bounds. We only saw this issue because :'to_s' goes through Ruby String processing before being made into a Symbol. Sort of a weird combo but it is possible this bad code in Symbol.getName() could be causing other issues? [Note: this will only be effective fix for 9.1. For 9.2 this is already fixed because we have switched to a completely different way of handling encoded identifiers.]
Yeah this was just another case of pretending unsafeBytes() has begin of 0 and .length or realSize(). Almost hard to imagine any of these bugs could still exist...And bytelist_love is totally different now so this code I fixed does not exist there (and this works fine there). |
Environment
jruby 9.1.16.0 (2.3.3) 2018-02-21 8f3f95a Java HotSpot(TM) 64-Bit Server VM 25.162-b12 on 1.8.0_162-b12 +jit [linux-x86_64]
Linux 4.14.14-1-ARCH #1 SMP PREEMPT Fri Jan 19 18:42:04 UTC 2018 x86_64 GNU/Linux
Expected Behavior
Actual Behavior
The text was updated successfully, but these errors were encountered: