Ian Mackenzie

Results 122 issues of Ian Mackenzie

Something like ```elm Point2d.angleFrom : Point2d units coordinates -> Point2d units coordinates -> Point2d units coordinates -> Angle ``` and maybe also ```elm Point3d.angleFrom : Point3d units coordinates -> Point3d...

- [ ] `Axis2d.intersectionWithBoundingBox : BoundingBox2d -> Axis2d -> Maybe LineSegment2d` - [ ] `Axis2d.intersectionWithTriangle : Triangle2d -> Axis2d -> Maybe LineSegment2d` - [ ] `Axis3d.intersectionWithBoundingBox : BoundingBox3d -> Axis3d...

- Explain why it cannot return a signed angle - Suggest projecting both directions into a reference sketch plane and measuring angle in that plane Perhaps also/alternatively add a function...

Do a pass through the docs and point out where types/modules come from other packages; may also be worth adding a section to the README like "Relationship to other packages"...

- [ ] `LineSegment2d.signedDistanceAlong : Axis2d -> LineSegment2d -> Interval` - [ ] `LineSegment2d.signedDistanceFrom : Axis2d -> LineSegment2d -> Interval` - [ ] `LineSegment3d.signedDistanceAlong : Axis3d -> LineSegment3d -> Interval`...

help wanted
Hacktoberfest
good first issue

Several `elm-geometry` constructors use a similar naming pattern using `with` as part of the name, e.g.: ```elm Circle2d.withRadius : Quantity Float units -> Point2d units coordinates -> Circle2d units coordinates...

breaking change

Especially if `elm-geometry` gains support for `Int`-valued geometry as part of #66, it would likely be useful to add dedicated functionality to convert back and forth between `Int` and `Float`-valued...

question

Currently, `rotateAround` functions are optimized for partial application - they cache computed sines/cosines etc. in a returned lambda, which is then just immediately called and discarded if `rotateAround` is called...

Hacktoberfest

It would be safest for functions like `Arc2d.centerPoint`, `Arc2d.radius` and corresponding functions in `Arc3d` (including 3D-specific ones like `Arc3d.normalAxis`) to return `Maybe` values when the arc swept angle is zero...

breaking change

Should still be very unlikely to result in a naming conflict, and would have a couple of advantages: - Would allow for some shorter function names: - `ArcLength.parameterization` instead of...

breaking change