click on the line number on github and copy the url from the browser
youc an also select ranges etc
also, nice that you found gitter
chat is a nice complement to issues
For sure. It's great to have a forum to directly ask questions and discuss things around libraries.
ok, that message does not make things very clear, was probably I who wrote it, we should write something better
question is what to write?
I'm especially unsure because your suggestion to my original question is to do what that method does :)
reason for making the method obsolete is that it is in the category of useless helpers that don't make anything clearer
That makes sense, I guess the clarity issue may come from the word "projections" in the current comment. It's a bit ambiguous as to what is actually meant.
Also...someone on my team may end up packaging this project up (right now we are just building from source as we test some things out...)...If that happens would anyone here be interested on what he does?
I agree with your definitions, however Line2D does not reflect the definition you gave. I am just trying to get a gauge on what direction the whole library is moving towards.
I think I implemented Line2D in an unfortunate way.
lately there has not been much direction
Have you seen system.numerics btw?
It looks pretty nice
LIneSegment2D is more or less a name change from Line2D to free up the namespace to implement LIne2D as per the definition Johan gave for a line. But since releases seem to be a blocking point, the sequence of change got rather lost
the idea was first LineSegment2D/3D. Then deprecate LIne2D/3D, then remove Line2D/3D. Then reintroduce support for actual geometric lines
It was envisaged to do this in separate releases to allow existing users of the library time to adapt their code... but that was back when we kind of thought we could do a series of releases in sequence, roughly one a month. Smaller evolutions
Hello, is there any documentation for this package?