Baidyanath Kundu

@grimmmyshini yeah the culprit is an `ImplicitCastExpr` which we can verify when we call dump on the expression on which `MakeCladTapeFor` is used: ``` ImplicitCastExpr 0x5555629ce030 'float' `-ImplicitCastExpr 0x5555629ce018 'int'...

> Which AST node causes the type mismatch? Is it `clad::push(_t1, a)`? Yeah this node causes type mismatch because the type of `_t1` is determined using this AST node: ```...

Is this repo dead?

@spacewafer vissarion has been working on this for quite a while as you can see it in his [fork](https://github.com/vissarion/geometry/tree/feature/shortest_points_new)

@vissarion , yeah sure. The below example uses a 3D multipoint as an input and gives out a 3D multipoint as an output. The input provided is that contains the...

I think we should give a compile time warning stating that `Supplied argument(s) is/are 3D but will be treated as 2D`. We can generalize the template stating _supplied type_ isn't...

I would like to work on this. Is what @mloskot suggested final or does this need more inputs?

@mloskot 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...

> You need to link issue or PR or whatever you are talking about. I was talking about #670 > > This seems like a detect approach > > I'm...

> Do I understand correctly that Plotly is only able to draw plots, so it is not for drawing geometries and what this PR does is allowing to represent Boost.Geometry...