Opened 3 years ago

Last modified 3 years ago

## #20387 new defect

# Deprecate support for finite rings in `LinearCode`

Reported by: | jsrn | Owned by: | |
---|---|---|---|

Priority: | major | Milestone: | sage-7.2 |

Component: | coding theory | Keywords: | beginner, linear_code, finite_ring, ring_code |

Cc: | dlucas, ppurka | Merged in: | |

Authors: | Reviewers: | ||

Report Upstream: | N/A | Work issues: | |

Branch: | Commit: | ||

Dependencies: | Stopgaps: |

### Description

Purportedly, `LinearCode`

supports making codes over finite rings. The documentation states only that the ring needs to support "various methods" such as matrices over the ring has a `rank`

function.

However, the underlying assumption in almost all of the code in `LinearCode`

is and has always been that the code is over a finite field. Just because one or two random methods don't (currently) blow up on a code over a finite ring doesn't mean we should claim to support finite rings since all the other functions *do* blow up or, worse, return wrong or non-sensical results. No-one writing methods for `LinearCode`

is ever thinking of finite rings.

Concrete functions that don't properly work over (most) finite rings: `dimension`

, `cardinality`

, `automorphism_*`

, `unencode`

, `canonical_representative`

, `characteristic_polynomial`

, `parity_check_matrix`

. And there are many more.

The only sensible way forward is to honestly say that we don't support finite rings. If someone really needs finite rings, it is clear that this is yet to be implemented, and that person would hopefully do it. Note that #19345 provides a step in this direction.

**Note:**See TracTickets for help on using tickets.