JuliaGeometry / JuliaGeometry/CoordinateTransformations.jl
Typed transformations
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 185
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
Back in #1 we decided that Transformation was agnostic about input and output coordinate types. I still think this was the right thing, but sometimes you may want a bit more checking of the input and output types. This is perfectly possible when creating a custom Transformation functor, but it would be nice to be able to reuse the composition and inverse rules of existing types like AffineMap and LinearMap.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the existing Transformation, AffineMap, and LinearMap types, focusing on their composition and inverse rules. Determine how typed input and output checks could be added while preserving those reusable rules; done means the requested typed transformations are supported without changing the agnostic behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100