JuliaConstraints / JuliaConstraints/ConstraintProgrammingExtensions.jl
Benchmark VectorDomain
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 24
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
For ConstraintSolver.jl's VectorDomain, @Wikunia uses a matrix, while this package's VectorDomain uses a set of vectors. We should test the performance of both approaches before making a final decision on the best way to represent this set, but also brainstorm about the pros and cons of each approach.
Matrix
Pros:
- easy to enforce that each element has the same size (Julia does it when the user builds a matrix)
Cons:
- enforces some kind of order between the elements, while this is not really required
Set of vectors
Pros:
- no order between the elements
Cons:
- the constructor must enforce that each element has the same size
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 with ConstraintSolver.jl's VectorDomain and compare the package's set-of-vectors representation with the matrix approach used by @Wikunia. Benchmark both approaches and document their performance, pros, and cons; the work is done when it supports a final representation decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100