#15882: Implement a catalog for crystals
-------------------------------------+-------------------------------------
Reporter: tscrim | Owner: sage-combinat
Type: enhancement | Status: new
Priority: major | Milestone: sage-6.2
Component: combinatorics | Resolution:
Keywords: crystals catalog | Merged in:
Authors: Travis Scrimshaw | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
public/combinat/crystals/catalog | 56a29b8c91230b155f45eb9b1f643b0e1caa7855
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by nthiery):
Thanks Travis! I haven't checked the code yet, but this will be a nice
improvement.
One thing I have been pondering for some time: at the end of the day, we
can expect that there will eventually be exactly two entry points for
crystals in the global name space, namely {{{crystals}}} and
{{{Crystals}}} (indeed, once #10963 will be in, we will be able to
deprecate {{{FiniteCrystals()}}} and friends in favor of
{{{Crystals().Finite()}}}).
Would it make sense to push the logic even further and actually have a
single entry point, which probably should be {{{Crystals}}}? In other
words, could the category also play the role of catalog of
implementations? Maybe something like
{{{Crystals.catalog.CrystalOfLetters(...)}}} though this is a bit
heavyweight.
Of course this question is not just about crystals, but could apply to
groups, posets, ...
Anyway, just food for thought for after this ticket.
--
Ticket URL: <http://trac.sagemath.org/ticket/15882#comment:2>
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.
