-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Method overwriting by an ambiguity should also invalidate the method cache #21965
Conversation
With JuliaStrings/LegacyStrings.jl#8 fixed (and a new LegacyStrings version tagged), |
Should be packported? |
As long as we don't backport #21892 (and I guess we won't), there AFAICT is no need to backport this. The fact that a method is still callable despite there being an ambiguity should rarely be a problem. OTOH, this can be a breaking change by uncovering bugs (as it was for LegacyStrings), which makes it an unlikely backport candidate. |
Your benchmark job has completed - possible performance regressions were detected. A full report can be found here. cc @jrevels |
The performance regressions should all be noise, and I guess the travis OSX failure is unrelated, but I don't really know what happened there. |
fix #21963
DO NOT MERGE (until JuliaStrings/LegacyStrings.jl#8 is fixed)