FinField: use concrete types for sub-/overfield morphisms to improve inferrability #1961
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.
Both functions modifying these dicts already restrict the types in the same way:
Without this PR:
(Any further calls will be fast since it is already compiled)
With the changes in this PR:
Without the changes here the return type of
Nemo.domain(::FinFieldMorphism)
which is used insideNemo.intersections(::FinField,::FinField)
cannot be inferred. Then the compiler seems to look at all possibleembed(Any,Any)
functions which takes very long, especially the branch forHecke.embed(S::ZZLat, G::ZZGenus)
.For Nemo alone the difference is less significant, but it does improve allocations during compilation quite a bit.
0.47.5
:this PR:
cc: @flenzen @thofma @fingolfin
flamegraph for snoop_inference without this PR: