Opened 7 years ago

Last modified 18 months ago

#18343 needs_review defect

creation of libgap integers are slow (if not buggy)

Reported by: vdelecroix Owned by:
Priority: major Milestone: sage-duplicate/invalid/wontfix
Component: packages: standard Keywords:
Cc: Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description

  1. Creating libGAP integers from python int is broken
    sage: libgap(2r**61r)
    ...
    OverflowError: value too large to convert to int
    
    This is due to a cast to a C <int> in sage.libs.gap.* (Python integers do not necessarily fit into an int (though they do in a long)).
  1. Creating libGAP integers from Sage integers is very slow since it goes through the string representation! As GAP internally uses mpz it could be very fast.

Change History (1)

comment:1 Changed 18 months ago by embray

  • Milestone changed from sage-6.7 to sage-duplicate/invalid/wontfix
  • Status changed from new to needs_review

This would be fixed by #31404. Of course, this ticket should still be kept open until/unless that one is merged.

Note: See TracTickets for help on using tickets.