-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
remove bad method specialization from cache #39429
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
Conversation
This was inserting a method with signature [Int, Int], rather than Tuple{typeof(+), Int, Int}. Fix that and add a test for it so it doesn't happen again.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Jameson! :)
Can you explain the bug? Specifically, is the "Revise-oriented precompiles" just a cleanup, and the real bug is in |
The indentation changes are just noise. Here's the diff without it: https://github.com/JuliaLang/julia/pull/39429/files?diff=unified&w=1. Specifically, it was just passing in the wrong objects to this function, and those were getting processed without checking their types (in C). |
This was inserting a method with signature [Int, Int], rather than Tuple{typeof(+), Int, Int}. Fix that and add a test for it so it doesn't happen again. (cherry picked from commit b9f8b8b)
This was inserting a method with signature [Int, Int], rather than Tuple{typeof(+), Int, Int}. Fix that and add a test for it so it doesn't happen again. (cherry picked from commit b9f8b8b)
This was inserting a method with signature [Int, Int], rather than Tuple{typeof(+), Int, Int}. Fix that and add a test for it so it doesn't happen again.
This was inserting a method with signature [Int, Int], rather than Tuple{typeof(+), Int, Int}. Fix that and add a test for it so it doesn't happen again.
This was inserting a method with signature [Int, Int], rather than Tuple{typeof(+), Int, Int}. Fix that and add a test for it so it doesn't happen again. (cherry picked from commit b9f8b8b)
Noticed this bug (which was moved in cc1623b, but originally introduced in 4c4e078) while exploring code internals
Those were backported, so this needs to be also.