#18158: `__getitem__` for libGap_Element
------------------------------+------------------------
Reporter: vdelecroix | Owner:
Type: defect | Status: new
Priority: critical | Milestone: sage-6.6
Component: interfaces | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
------------------------------+------------------------
Comment (by vdelecroix):
Replying to [comment:3 vbraun]:
> It does break the rule of least surprise, e.g.
> {{{
> sage: l = some_computation()
> sage: l
> [ 1, 2, 3 ]
> sage: l[0] # guess what?
> }}}
I agree with your example. On the other hand, gap permutations starts at 1
and it is coherent with their lists starting at 1.
More importantly, for who is intended the gap/libgap interface objects
(and more generally Sage interface objects):
- everybody
- Sage programmers
- users knowing gap (pari, singular, etc)
- ?
I rarely use `._pari_()`, `._gap_()` when doing actual computations. When
I do, it is that Sage is lacking some interface.
Vincent
--
Ticket URL: <http://trac.sagemath.org/ticket/18158#comment:4>
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 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 http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
