Improve type stability for tryparse VersionNumber#40557
Improve type stability for tryparse VersionNumber#40557KristofferC merged 2 commits intoJuliaLang:masterfrom rikhuijzer:type-stability-tryparse
Conversation
Co-authored-by: Simeon Schaub <simeondavidschaub99@gmail.com>
|
I think that the error on linx32 is unrelated, because the same occurs at #40523. |
simeonschaub
left a comment
There was a problem hiding this comment.
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.