[CORE] Native support for 2D and 3D vertices

[bobluppes]

2D and 3D vertices

In order to support geometric algorithms (such as Delaunay triangulation) we want to natively support geometric vertices. The goal of this issue is to implement a point_2d and point_3d class.

Along with these vertex specializations, we can then also provide specializations for geometric graphs (i.e. geometric_graph_2d and geometric_graph_3d).

Syntax

An initial idea for the (public) interface of the new classes is as follows:

(note that this is not set in store and merely serves as a starting point)

// point_2d.h
class point_2d {
  public:
    point_2d(double x, double y);
    
    [[nodiscard]] double x() const noexcept;
    [[nodiscard]] double y() const noexcept;
}

// point_3d.h
class point_3d {
  public:
    point_3d(double x, double y, double z);

    [[nodiscard]] double x() const noexcept;
    [[nodiscard]] double y() const noexcept;
    [[nodiscard]] double z() const noexcept;
}

// geometric_graph.h
template <typename EDGE_T, graph_type GRAPH_TYPE_V>
using geometric_graph_2d = graph<point_2d, EDGE_T, GRAPH_TYPE_V>

template <typename EDGE_T, graph_type GRAPH_TYPE_V>
using geometric_graph_3d = graph<point_3d, EDGE_T, GRAPH_TYPE_V>

This class should live in the graaf::geometric namespace under the (new) directory include/graaflib/geometric/.

Definition of Done

This issue is done when:

• The new classes are implemented
• The new classes has a javadoc-style comment for the entire class and for the public methods
• Appropriate tests are added under test/graaflib/geometric
  • A test coverage of at least 95% is reached

[bobluppes]

Won't do for now as we aim to keep the library general purpose. Keeping this in the issue list for future reference. If we see that this is a common use case among our users then we may reconsider.