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
is postcritically finite failure for extensions #25243
Comments
Author: Ben Hutz |
New commits:
|
Commit: |
Branch: u/bhutz/25243_pcf_fix |
comment:3
Fixed merge conflict with master, manually implemented the same code changes, and removed changes to deprecated code. Also have another test case:
New commits:
|
Changed branch from u/bhutz/25243_pcf_fix to u/gh-Torrencem/25243_pcf_fix |
Changed keywords from none to SI2019 |
comment:4
The following changed line's purpose is unclear to us. When we removed it, and changed the variable names, it seemed to still work well without it:
Is this line still necessary? |
comment:5
It had been necessary, unless extension/compositums do their own name collision resolution now, leaving the default names was regularly causing name conflict, so that tweak avoided that collision. |
comment:6
Did a little testing. It seems to no longer be an issue. I wasn't able to get an example that fails. Give this branch a try. |
Changed branch from u/gh-Torrencem/25243_pcf_fix to u/bhutz/25243_pcf_fix2 |
Reviewer: Jasmine Camero, Olivia Schwager |
Changed branch from u/bhutz/25243_pcf_fix2 to |
When the field extension needs to be extended there can be a conflict of variable names
Component: dynamics
Keywords: SI2019
Author: Ben Hutz
Branch/Commit:
9d99a13
Reviewer: Jasmine Camero, Olivia Schwager
Issue created by migration from https://trac.sagemath.org/ticket/25243
The text was updated successfully, but these errors were encountered: