#9054: create a class for basic function_field arithmetic for Sage
-----------------------------------------------------------------------------------------------+
    Reporter:  was                                                              
               |         Owner:  was                          
        Type:  enhancement                                                      
               |        Status:  needs_review                 
    Priority:  major                                                            
               |     Milestone:  sage-4.7.2                   
   Component:  algebra                                                          
               |    Resolution:                               
    Keywords:                                                                   
               |   Work_issues:                               
    Upstream:  N/A                                                              
               |      Reviewer:  Maarten Derickx, Julian Rueth
      Author:  William Stein, Robert Bradshaw, Maarten Derickx, Moritz 
Minzlaff, Julian Rueth  |        Merged:                               
Dependencies:  #9094, #11751, #9138                                             
               |  
-----------------------------------------------------------------------------------------------+
Changes (by saraedum):

  * status:  needs_work => needs_review


Old description:

> One of the first things we learned at Sage Days 21: Function Fields, is
> that it is not even possible to really define or even do arithmetic in
> function fields *at all* in Sage!  It's amazing that this most basic
> arithmetic still isn't supported, but it isn't (maybe it used to be via
> generic machinery, but got broken...?).  The point of this ticket is to
> create classes for standard function field structures, along with support
> for arithmetic.   This should be organized in a way similar to number
> fields.
>
> For this code, the main point is to establish an API that works solidly.
> It will be insanely slow.  A subsequent patch will make things fast.
>
> See also: #9069, #9051, #9094, #9095.
>
> Note that the dependancy on #9138 is only because of a really minor
> change in the doctests. This ticket already has a positive review so I
> suspect this will get merged first. If that ticket eventually gets
> rejected it will be trivial to rebase the patch withouth that ticket.
>
> ----
>
> Apply
>
>  1. [attachment:trac_9054-all-parts.patch]
>  1. [attachment:trac_9054_polynomial_base_field.patch]
>  1. [attachment:trac_9054_zero.patch]
>  1. [attachment:trac_9054_codomain.patch]
>  1. [attachment:trac_9054_doctest-2.patch]
>  1. [attachment:trac_9054-review.patch]
>  1. [attachment:trac_9054_undo_unittest.patch]
>  1. [attachment:trac_9054-invert_ideal.patch]
>  1. [attachment:trac_9054_is_function_field.patch]
>  1. [attachment:trac_9054_unique_factory.patch]
>  1. [attachment:trac_9054_cached_method.patch]
>  1. [attachment:trac_9054_maximal_order_member_check.patch]
>  1. [attachment:trac_9054_call_super_constructors.patch]
>  1. [attachment:trac_9054_maps_refactor.patch]
>  1. [attachment:trac_9054_doctests-3.patch]
>  1. [attachment:trac_9054_cleanup.patch]
>  1. [attachment:trac_9054_authors.patch]
>  1. [attachment:trac_9054_reference.patch]
>  1. [attachment:trac_9054_factor.patch]
>
> to the Sage library.

New description:

 One of the first things we learned at Sage Days 21: Function Fields, is
 that it is not even possible to really define or even do arithmetic in
 function fields *at all* in Sage!  It's amazing that this most basic
 arithmetic still isn't supported, but it isn't (maybe it used to be via
 generic machinery, but got broken...?).  The point of this ticket is to
 create classes for standard function field structures, along with support
 for arithmetic.   This should be organized in a way similar to number
 fields.

 For this code, the main point is to establish an API that works solidly.
 It will be insanely slow.  A subsequent patch will make things fast.

 See also: #9069, #9051, #9094, #9095.

 Note that the dependancy on #9138 is only because of a really minor change
 in the doctests. This ticket already has a positive review so I suspect
 this will get merged first. If that ticket eventually gets rejected it
 will be trivial to rebase the patch withouth that ticket.

 ----

 Apply

  1. [attachment:trac_9054-all-parts.patch]
  1. [attachment:trac_9054_polynomial_base_field.patch]
  1. [attachment:trac_9054_zero.patch]
  1. [attachment:trac_9054_codomain.patch]
  1. [attachment:trac_9054_doctest-2.patch]
  1. [attachment:trac_9054-review.patch]
  1. [attachment:trac_9054_undo_unittest.patch]
  1. [attachment:trac_9054-invert_ideal.patch]
  1. [attachment:trac_9054_is_function_field.patch]
  1. [attachment:trac_9054_unique_factory.patch]
  1. [attachment:trac_9054_cached_method.patch]
  1. [attachment:trac_9054_maximal_order_member_check.patch]
  1. [attachment:trac_9054_call_super_constructors.patch]
  1. [attachment:trac_9054_maps_refactor.patch]
  1. [attachment:trac_9054_doctests-3.patch]
  1. [attachment:trac_9054_cleanup.patch]
  1. [attachment:trac_9054_authors.patch]
  1. [attachment:trac_9054_reference.patch]
  1. [attachment:trac_9054_factor.patch]
  1. [attachment:trac_9054_order_category.patch]

 to the Sage library.

--

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9054#comment:61>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en.

Reply via email to