boostorg / boostorg/geometry

Cartesian distance fails to compile (This operation is not or not yet implemented)

Open
#1,092 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
517
Forks
232
PR merge metrics
No merged PRs in 30d

Description

Whatever geometry is used.
Boost is compiled with xcode 13.4.1

Example :
typedef boost::geometry::model::d2::point_xy point_t;
typedef boost::geometry::model::polygon poly_t;

point_t p(ray.m_origin.x, ray.m_origin.y);

poly_t poly;
poly.outer().push_back(point_t(R0.x, R0.z));
poly.outer().push_back(point_t(R1.x, R1.z));
poly.outer().push_back(point_t(L0.x, L0.z));
poly.outer().push_back(point_t(L1.x, L1.z));
poly.outer().push_back(point_t(R0.x, R0.z));

auto distance = boost::geometry::distance(p, poly);

We get :
Static_assert failed due to requirement 'boost::geometry::detail::static_assert_check::value' "This operation is not or not yet implemented."

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the provided C++ example with Boost.Geometry's point, polygon, and distance call on the stated Xcode setup. Trace the dispatch that produces the point_tag/areal_tag static assertion; done means the reported point-to-polygon distance compiles and the behavior is covered by an appropriate regression test.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.