On 5/1/24 14:33, Waldek Hebisch wrote:
OrderedField() : Category == Joint(OrderedIntegralDomain, Field)
'OrderedField' potentially says more than the Join.
Clear.
So to make 'OrderedField' useful we would have to annotate algebra
with several declarations like
> if C has OrderedRing and C has Field then OrderedField
Well, I could understand a line like
if % has OrderedRing and % has Field then OrderedField
But I would bet, in the declaration of a domain the programmer often
already knows whether or not % should export OrderedField.
If you really mean C and C would be a parameter of a domain/category,
then I agree with you, but actually also there if the parameter C
exports both OrderedRing and Field then why wouldn't it also export
OrderedField? Yes, there maybe cases where this is really so, but
shouldń't such cases be exceptions and rather maybe point to a not
perfect definition of the respective exports of C?
BTW: For domain we can write things like
SortedExponentVector == U32Vector
which basically says that 'SortedExponentVector' is an alias for
'U32Vector'. BUT ATM this is not supported for categories. You can
write:
I actually wonder where this might be useful.
Ralf
--
You received this message because you are subscribed to the Google Groups "FriCAS -
computer algebra system" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/fricas-devel/3b9857a8-0261-42a7-97e3-4116d6935cb1%40hemmecke.org.
