Subject: Re: [geometry] Report not yet implemented feature at runtime
From: Samuel Debionne (samuel.debionne_at_[hidden])
Date: 2015-03-13 10:03:52
> Just a heads up from a Boost.Geometry user. :)
> I think that using type erasure might be a good approach.
> Boost.Geometry already uses boost::concepts, which will be adopted
> into the C++ standard/TS with Concepts Lite. Andy Prowl proposed(1)
> virtual concepts, which is a runtime (type erased) concept, which
> corresponds to boost::type_erasure.
Thank you for the head up, interesting read, it seems that Type erasure
and virtual concepts are here to stay.
I don't think it will solve all my problems of input types that vary at
runtime, since a any_geometry<> type would be a mix of
different/incompatible concepts. That may help to reduce the number
instantiated template, having a single point type for all the xy, xyz,
xym xyzm variants. I'm going to give it a shot and report.
Geometry list run by mateusz at loskot.net