You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our implementation of hashing for RubyHash insertion just calls hashCode on the target object. This has only one implementation in our hierarchy that dynamically tries to call hash.
For some core types, this extra logic could be omitted as long as hash was still the built-in version. As it stands now, even with call site caching this code will be heavily contended and a potential bottleneck for hash access.
The text was updated successfully, but these errors were encountered:
Our implementation of hashing for RubyHash insertion just calls
hashCode
on the target object. This has only one implementation in our hierarchy that dynamically tries to callhash
.For some core types, this extra logic could be omitted as long as
hash
was still the built-in version. As it stands now, even with call site caching this code will be heavily contended and a potential bottleneck for hash access.The text was updated successfully, but these errors were encountered: