Fix some inference failures in Base.require call graph #44628
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I found another package, RoundingIntegers.jl, that invalidates
Base.require
, which is particularly bad to invalidate since it has to be recompiled before loading the next package; if it happens repeatedly it can substantially slow loading. I finally decided to just go through the JET report onBase.require
and fix most of the things that I could fix that weren't already being handled in #44500.I am not certain whether the change to
make_aliases
(always returning aVector{SimpleVector}
) is wise, but the tests pass so 🤷.