Fix performance issue in hilbn and friends #9
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.
Hi! I was playing with the Hodge diamonds of K3^[n] and I noticed there is a huge performance issue. It appears that power series does not allow access of individual coefficients, and
series.coefficients()
creates a large dictionary which contains a lot of redundant info. So it's a lot faster to convert a power series to a polynomial then access its coefficients.The same issue happens in
nestedhilbn
andcomplete_intersection
too.Also I fixed the variable names in
cyclic_cover
:)