Skip to content

Conversation

@enebo
Copy link
Member

@enebo enebo commented May 8, 2024

In implementing the feature I took the least complicated route. We get a new Operand and in JIT we just add a second chilled boolean vs trying to shave this to a three-state value.

One uncertainty is that I mark chilled as both frozen and chilled in RubyString flags. I did this because there are lots of isFrozen() checks in our codebase and I would like to fail fast if we find a path where chill should convert to mutable and we miss it. If we were certain we could probably only set chill flag and then check that in frozen?.

In implementing the feature I took the least complicated route.  We
get a new Operand and in JIT we just add a second chilled boolean vs
trying to shave this to a three-state value.

One uncertainty is that I mark chilled as both frozen and chilled in
RubyString flags.  I did this because there are lots of isFrozen() checks
in our codebase and I would like to fail fast if we find a path where
chill should convert to mutable and we miss it.  If we were certain we could
probably only set chill flag and then check that in `frozen?`.
@enebo enebo added this to the JRuby 10.0.0.0 milestone May 8, 2024
@enebo enebo merged commit ac513f5 into jruby:9.5-dev May 8, 2024
@enebo enebo deleted the chilled branch March 4, 2025 18:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant