[Olena] #231: Split the implementation of graph in two : fast vs safe

#231: Split the implementation of graph in two : fast vs safe -------------------------+-------------------------------------------------- Reporter: levill_r | Owner: Olena Team Type: enhancement | Status: new Priority: major | Milestone: Olena 1.1 Component: Milena | Version: 1.0 Keywords: | -------------------------+-------------------------------------------------- (Re)start a branch revamp-graph: * Create a safe version of `util::graph` (as well as associated types : vertex, edge), having the same interface as the original. * Then remove all unnecessary code from the current version to have a truly fast version (in particular, remove pointers to graph in vertex and edge descriptors). * Factor as much as possible, of course. * And document. * Further work: try to apply the same recipe to complexes, and adjust `p_complex`, `complex_image`, etc. as well, to support both implementations (fast and safe), possibly with a mechanism selecting one version by default. -- Ticket URL: <https://trac.lrde.org/olena/ticket/231> Olena <http://olena.lrde.epita.fr> Olena, a generic and efficient C++ image processing library.

#231: Split the implementation of graph in two : fast vs safe -------------------------+-------------------------------------------------- Reporter: levill_r | Owner: Olena Team Type: enhancement | Status: new Priority: major | Milestone: Olena 2.x Component: Milena | Version: 1.0 Keywords: | -------------------------+-------------------------------------------------- Changes (by lazzara): * milestone: Olena 2.1 => Olena 2.x -- Ticket URL: <https://trac.lrde.org/olena/ticket/231#comment:1> Olena <http://olena.lrde.epita.fr> Olena, a software platform dedicated to image processing.
participants (1)
-
Olena Trac