Tommy Hofmann
Tommy Hofmann
Yeah, sure, one can and should then use `Map{
We need one name for both (univariate and multivariate) cases, so maybe `coefficients_and_exponents`. On the other hand, I had a quick chat with @fieker and maybe we want `coefficients` to...
Hmm, I think this is a good idea. There are some functions that we expect and that we define e.g. for `Float64` or `BigInt`. Since they probably don't want to...
Of course my approach only works if the parent is uniquely determined by the type, which is for example the case for the types @jmichel7 is providing. I don't think...
I don't even think that we need wrapper. I want to try to cook something up and see if it works with his cyclotomic elements.
Yes, it should be used recursively. We bolted it onto the system later and wanted to be backwards compatible. That is why it is a keyword argument with default value....
@tthsqe12 does want to call derivation on the coefficients of the polynomials, so something like ``` map_entries(f -> map_coeffs(z -> derivative(z, b), f), mat) ``` In a polynomial ring `F[x]`,...
Why was your point getting obfuscated? This is just about having a nice way to turn maps on `F` to maps on `F[x]` by applying it to each coefficient. This...
I don't know yet. The problem is that julia treats our matrices like anything else: ```julia julia> vcat("x", [1 2]) 2×2 Matrix{Any}: "x" "x" 1 2 julia> vcat("x", [1 2;...
Julia expects at various places to have `zero` working on the type. This does not work for us.