#16622: Deprecate Hypergraph in favor of IncidenceStructure
-----------------------------------------+------------------------
Reporter: ncohen | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-6.3
Component: combinatorial designs | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
-----------------------------------------+------------------------
Comment (by ncohen):
Yo !
> I'm not sure one should `deprecate` one in favour of the other. They are
different names of the same object, as far as I am concerned. (IMHO
"hypergraph" is a more common name, and there has been a lot of work done
in this terminology, especially in TCS people prefer this terminology).
Hmmm... I prefer Hypergraph too, but the most interesting code is in
`IncidenceStructure`. What I am implementing right now does the following
:
1) move the features of Hypergraph that are not available in
`IncidenceStructure`
2) add a deprecation warning saying that in the future Hypergraph will be
an alias for `IncidenceStructure` but that the input/output are different
so that people should use `IncidenceStructure` directly in the meantime
I made a mistake with git commands, and as a result all files were
"touched" and I recompile Sage right now... In the meantime I will make
sure that all doctests that used to work on `Hypergraph` still work, and I
will update the doc/doctests of their new `IncidenceStructure`
counterparts.
I have nothing against changing the name of `IncidenceStructure` by the
way. Vincent wrote a patch recently (#16553) which showed that it had been
written with "Block Design" in mind, which is not what "incidence
structure" means. What do you think ? Anyway, if we eventually merge the
two we will have to change the input of one for the inputs of the other,
so this way is as good as any.
Besides, I suspect that nobody besides me knows that Sage has a Hypergraph
class. I began this patch because of some emails with Stefan, which made
us notice that we are already doing the same work twice in matroids and
designs when it comes to hypergraphs.
Nathann
--
Ticket URL: <http://trac.sagemath.org/ticket/16622#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/d/optout.
