Paul Zinn-Justin

so with this PR: `iterators.m2` needs `expressions.m2` which needs `max.m2` which needs `fold.m2` which needs `iterators.m2`... how are we supposed to deal with those circular dependencies?

a `NumericalImplicitization` test runs oom, don't think it's related to this PR?

I use the workaround below. Alternatively, one can use my package `Factor` (still not PRed due to annoying incompatibilities with some code that uses `factor`) which completely redefines everything in...

I don't think expressions is the solution since by definition you can't do mathematical operations on them. here's the demo, BTW: https://www.unimelb-macaulay2.cloud.edu.au/?user=xxx#chat the first version ("old way") is just the...

BTW Factor hasn't been updated in a while, in particular not since factor.m2 (sigh, lowercase vs uppercase) was introduced. there's also an issue with monomial ordering that needs fixing.

> What do you think about this? > > ```m2 > Divide + Divide := (x,y) -> if denominator x === denominator y then new Divide from {numerator x +...

what I meant was, `expression 1 + expression 2` will give you `1+2`, whereas `expression 0 + expression 2` will give you `2`. BTW I think we're digressing from the...

yes, another type, like an actual ring element

Actually this is more or less exactly what my package `Factor` does, cf #1645 (at the time I gave up on the PR because Macs are unable to distinguish `factor.m2`...

That being said, there's a subtle difference between what `Factor` does and what you @mikestillman suggest: `Factor` introduces a type `FactorPolynomialRing` which is a descendent of `PolynomialRing`. You suggest a...