Fix compatibility of Tuple's hash function#3460
Conversation
youknowone
left a comment
There was a problem hiding this comment.
The change looks great, but by looking at the CI result, range() hash must follow the reuslt of tuple. Could you also update range.__hash__ in the same way?
You can extract hash function like fn tuple_hash(elements: &[PyObjectRef], vm: &VirtualMachine) and call it form PyTuple::hash like tuple_hash(zelf.as_slice())
|
The new bug is bug of |
|
@coolreader18 do you have any idea? |
cc65be9 to
c2955f8
Compare
c2955f8 to
1d80da9
Compare
WalkthroughThe updates remove the Changes
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (2)
💤 Files with no reviewable changes (1)
🧰 Additional context used🧠 Learnings (2)📓 Common learningsvm/src/builtins/tuple.rs (3)🔇 Additional comments (2)
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
youknowone
left a comment
There was a problem hiding this comment.
Great, I have no idea which certain point made the changes, but it now works!
Change hash function implementation of Tuple to compatible with CPython's implementation.
Summary by CodeRabbit