Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
registered types vs existing models: within function compilation error #364
Comments
awulkiew
was assigned
by barendgehrels
Nov 9, 2016
|
Thanks! |
awulkiew
added the
bug
label
Dec 27, 2016
awulkiew
closed this
Dec 27, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
daniel-j-h commentedSep 10, 2016
I have the following use-case: check if a linestring is within a polygon.
Coordinate system is Spherical Equatorial.
The support-matrix in the documentation says this should work.
When I use the existing Boost.Geometry linestring and polygon models the
function call compiles fine. But when I'm switching out the existing Boost.Geometry linestring model with my own type (which I registered as a linestring) compilation fails.
Here is a small self-contained test case reproducing this issue:
This is surprising to me since both types are spherical equatorial, float precision, degree unit. There is no semantic difference from what I can see. I expected them to behave identically.
Here is the full error log. Boost version is 1.62 beta1.
https://gist.github.com/daniel-j-h/64bae0c01caaff30c2e40d27f7a98406