Tommy Hofmann

Yes, I think this is intended. One "problem" is that, `i,j=gens(S, ["i","j"])` is done recursively, so first `_, i = QQ["i"]` is constructed and then `_,(_,j)) = QQ["i", "j"]` and...

I think the documentation wants to say, that you can do the following: ``` julia> coeff(i, [1]) 1//1 julia> coeff(i, [1, 0]) 1//1 ``` Also this works: ``` julia> S(collect(coefficients(i)),...

Hm, in principle, this should work. Since the printing is quite convoluted, do you mind sharing what the end goal is?

What I do not understand yet is the relation to expressify. Since expressify for types defined in AbstractAlgebra cannot handle arbitrary properties that are stored in the IOContext, or that...

Hm, the printing works as follows. For AbstractAlgebra types, where printing is done via expressify, it is roughly as follows: ``` show(io, x) -> show_via_expressify(io, x) -> println(io, obj_to_string(canonicalize(expressify(x, context))))...

Here is a working example. The `dict` should hold the options. ``` julia> struct MyType end julia> function AbstractAlgebra.expressify(M::MyType; context = context) @show typeof(context.dict) opt = get(context, :youroption, false) if...

Yes, this will be a tad more tricky. Is there a specific reason why you want to manually adjust the REPL IO context and use that to control the printing?...

Chances are very low that this will be implemented. Is it really the `iszero` check? Do you use `MPolyQuoElem` for the arithmetic? I just noted that the `MPolyQuoElem` are very...

Yes, looks fine to me. Do we actually document somewhere which functions produce values that can safely be used as the first argument in `mul!` and friends?

With this ticket in mind, we don't need the PR here, as !-functions are not allowed to mutate the entries of the output. The problem is that the `add!` function...