We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I think all functionality of HeckeMap can be instead added to the abstract AbstractAlgebra.Map type. Then, HeckeMap is no longer needed.
HeckeMap
AbstractAlgebra.Map
Furthermore, similar changes can be done with Hecke.MapFromFunc and AbstractAlgebra.FunctionalMap.
Hecke.MapFromFunc
AbstractAlgebra.FunctionalMap
This would simplify and unify the usage and extensibility of map types everywhere from AbstractAlgebra up to Oscar.
The text was updated successfully, but these errors were encountered:
After talking to @fieker and @thofma we decided to keep everything as is until there are some serious reasons to change.
Sorry, something went wrong.
No branches or pull requests
I think all functionality of
HeckeMap
can be instead added to the abstractAbstractAlgebra.Map
type. Then,HeckeMap
is no longer needed.Furthermore, similar changes can be done with
Hecke.MapFromFunc
andAbstractAlgebra.FunctionalMap
.This would simplify and unify the usage and extensibility of map types everywhere from AbstractAlgebra up to Oscar.
The text was updated successfully, but these errors were encountered: