-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Improve type stability for tryparse VersionNumber #40557
Improve type stability for tryparse VersionNumber #40557
Conversation
Co-authored-by: Simeon Schaub <simeondavidschaub99@gmail.com>
I think that the error on linx32 is unrelated, because the same occurs at #40523. |
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.
Did you confirm with SnoopCompile that this fixes the invalidations? Otherwise LGTM
No, sorry. I did not do that. That would require building Julia from source and then running SnoopCompile on the package again, am I right? |
Wouldn't all the other methods that call |
I think I misunderstood: the methods invalidated are methods that call |
You could actually also click on |
On the CI build:
|
Thank you for the advise. I will do that before I submit any new PRs on invalidations. 👍
Thank you for checking! |
Co-authored-by: Simeon Schaub <simeondavidschaub99@gmail.com>
Co-authored-by: Simeon Schaub <simeondavidschaub99@gmail.com>
Co-authored-by: Simeon Schaub <simeondavidschaub99@gmail.com>
I noticed that LaTeXStrings is causing 297 method invalidations:
Specifically, the invalidation tree starts with
If I understand invalidations correctly, this invalidation will happen for any package which defines a new
firstindex(::T)
whereT isa AbstractString
. Although they can fix it by also definingmatch(r::Regex, T)
; it is probably a good idea to avoid these invalidations altogether.