#14912: UniqueRepresentation tutorial could use more love
--------------------------------------------+-----------------------------
Reporter: darij | Owner:
Type: defect | Status: needs_review
Priority: major | Milestone:
Component: documentation | Resolution:
Keywords: documentation, structure | Merged in:
Authors: Simon King | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Dependencies:
Stopgaps: |
--------------------------------------------+-----------------------------
Comment (by SimonKing):
Hi Darij,
Thank you for fixing the typos!
Replying to [comment:17 darij]:
> Thanks for the patch, which made several things clear to me (probably
not enough to be able to decide whether to use factories or unique rep --
but at least a good idea how to).
> ... I don't have the competence to do it; I barely understood the
`UniqueRepresentation` part and I know about nothing on Python's OOP
In a way, this means that you are fully qualified as a reviewer. This is
about documentation, and thus if you think that some points are still not
addressed then you should speak up! What information do you find missing?
Is it
- the definition of cached/unique representation?
- the design pattern: Why should one want to have cached/unique
representation?
- how to implement a cached/unique representation?
- Python background: What is a metaclass? What happens during
instantiation of a class?
- how to avoid pitfalls?
- else?
--
Ticket URL: <http://trac.sagemath.org/ticket/14912#comment:18>
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/groups/opt_out.
