Mateusz Łoskot

@sudo-panda If my comment does not receive any responses and if my suggestion _seems sensible to you_, and you are willing to give it a go, then I'd suggest you...

> Since this appears to be closely related to the header file I am already working on, do you think it will be better if I let that one get...

@Siddharth-coder13 See https://github.com/boostorg/geometry/issues/368#issuecomment-719465037

FYI, related comments posted in https://github.com/boostorg/geometry/pull/782#issuecomment-743275433

@Siddharth-coder13 Somehow this PR #789 and PR #782 have become a mess and they both contain the same commits (e.g. `Defined a geometry for polyhedron` that is `0961662e6e45878eda378f85dd734ae1922f7110`). I have...

It's unfortunate. The 1 needs to be in the other separate PR and 2+3 as a separate feature in this PR. I understand this may make your Git operations less...

I'd strongly suggest to not to close any existing PRs and to not to open any new PRs. > 1. Prefix wkt:z for 3d geometries. This should be in the...

@Siddharth-coder13 Please, hit the "Resolve conversation" for the items that you have addressed. This way, we can see what's been done and what's not.

I hope `QPoint` is not a polymorphic type. With Boost.Geometry your best bet is to use value types (as defined by Alexander Stepanov), so try to get rid of the...

> I known boost::geometry aims to GIS I don't entirely agree with this statement. The documentation is quite clear about how it uses the OGC specs, in https://www.boost.org/libs/geometry/doc/html/geometry/introduction.html it says...