-
Notifications
You must be signed in to change notification settings - Fork 188
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
Errors with _id2ref
when using frozen_string_literal
magic comment?
#2358
Comments
Thank you for the detailed report! The |
A fix for existing TruffleRuby versions would be to avoid using |
Many thanks for your quick response! I'm certainly not wedded to that code as it is - I'd be more than happy to refactor it once I am certain that I fully understand it (it's not mine originally, you see) 😄 Thanks! |
I think you'll find your
|
It does work with JRuby but we have to turn ObjectSpace on for the tests, which I know is not ideal. I'd be very happy to rid myself of that bit of code! I'll stare at it a bit tonight and see if I can figure out what it's doing... |
I can see what it's doing and why - it's hard to pass in a reference to an object to an |
Actually neither |
Thank you both @eregon, @chrisseaton for your attention and help with this! |
…rals (#2358) PullRequest: truffleruby/2666
Just to clarify, the _id2ref bug is fixed in beb45b8 (the issue was automatically closed by the commit fixing it). |
I have no idea what or where this bug really is, but as the behaviour I'm seeing is only in TruffleRuby I thought I'd submit here to see if you folks have any thoughts.
I am doing some work on rubyzip and I finally got around to adding the
frozen_string_literal: true
magic comment throughout the library. Now this is in place my CI is failing on TruffleRuby in GitHub Actions. This is the only change that has been made between a passing CI and failing CI:Actions is using TruffleRuby version 21.1.0 and TruffleRuby-head, which are both failing. I have version 20.3.0 on my local machine and all works fine!
The error is as follows:
Which is caused by a test that makes heavy use of meta-programming, unfortunately:
assert_forwarded
is where_id2ref
is called and is defined here:Any thoughts gratefully received! Many thanks.
The text was updated successfully, but these errors were encountered: