Hi Samuel.

On 19/05/2014 11:15 πμ, sdebionne wrote:
>
> In include/boost/geometry/algorithms/distance.hpp:
>
> > +        return dispatch::distance<Geometry1, Geometry2, Strategy>::apply(geometry1, geometry2, strategy);
> > +    }
> > +
> > +    template <typename Geometry1, typename Geometry2>
> > +    static inline typename result_of::distance<Geometry1, Geometry2, default_strategy>::type
> > +    apply(Geometry1 const& geometry1, Geometry2 const& geometry2, default_strategy)
> > +    {
> > +        typedef typename detail::distance::default_strategy
> > +            <
> > +                Geometry1, Geometry2
> > +            >::type strategy_type;
> > +
> > +        return dispatch::distance<Geometry1, Geometry2>::apply(geometry1, geometry2, strategy_type());
> > +    }
> > +};
> > +
>
>     In the unit test, I would like to see the variant defined as variant
>
> Just to be sure, is distance implemented for all the combinations of 
> these geometries and with the default and say the haversine strategies 
> ? If not, what combinations are supposed to fail to compile ?
>

Unless I have made a mistake, Cartesian distances work for all geometry 
combinations.
I have not worked yet with spherical geometries, so I can only speculate 
what works and what does not in the current setting. Since unit tests 
are passing everything that was tested in spherical coordinates in boost 
1.55 still works for the develop branch.

- m.

> —
> Reply to this email directly or view it on GitHub 
> <https://github.com/boostorg/geometry/pull/26/files#r12783336>.
>