> That would completely over-engineer things, be backwards incompatible, and
> would make users hate us. This is why we have exceptions.
Stick to that "would make users hate us" thought and look at what we have:
- A method that "sometimes work, and sometimes does not", because it
does not apply to all instances of its class
- Mathematically speaking, this method cannot even be *defined* on the
object to which it belongs (the order does not always exist)
- No documentation of whenever this function can be expected to work
(in particular no warning)
- Unclear error message when it fails:
sage: SetPartition([{'a','b','c'}]).to_permutation()
...
TypeError: cannot concatenate 'str' and 'int' objects
If what I propose is "over engineering", do you have anything better?
Nathann
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
