Changes between Initial Version and Version 1 of Ticket #31266, comment 15


Ignore:
Timestamp:
Jan 21, 2021, 11:16:04 PM (2 years ago)
Author:
jhpalmieri
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #31266, comment 15

    initial v1  
    1 For what it's worth, `sage/categories/modules_with_basis.py` has separate `tensor` methods for parents and elements. Same with `sage/categories/crystals.py`. A few other files have just a single `tensor` method for parents, which I am assuming works for both parents and elements. I don't know if there was any overarching scheme (perhaps a single method wouldn't work for some reason for those two cases?), but it might be good to have a policy. The `tensor` method in `modules_with_basis` says in its docstring
     1For what it's worth, `sage/categories/modules_with_basis.py` has separate `tensor` methods for parents and elements. Same with `sage/categories/crystals.py`. A few other files have just a single `tensor` method for parents, which I am assuming works for both parents and elements. I don't know if there was any overarching scheme (perhaps a single method wouldn't work for some reason for those two cases?), but it might be good to have a policy. The `tensor` method for elements in `modules_with_basis` says in its docstring
    22{{{
    33FIXME: is this a policy that we want to enforce on all parents?