CoCoA » CoCoALib

Proposal: create two functions for computing radicals

• radical which also tries hard to compute a GB for the result
• RadicalWithoutGB which tries to be quick, but may produce a result without GB

The argument goes: if someone computes the radical then they likely want to use it for further computation, so it will be helpful to have the GB.
If someone just needs any set of gens of the radical then they can use the potentially faster fn RadicalWithoutGB.

What should the user interface be like?

• two fns with separate but similar names? (what names?)
• one fn with an optional arg saying to compute faster (and possibly produce no GB)