maximwebb / maximwebb/polytope
Re-write in rust
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
This is a bit off topic but I was wondering if this project would ever be interested in moving to Rust were it has high emphasis on doing things right with memory and have concurrency built in hopefully prevent thread problems and still allows for custom garbage collection.
Everyone knows that C++ is slow, unsafe and hasn't got a cute mascot (attached for reference).
I have also attached a flowchart which should help weigh up the pros and cons of writing the project in a useful language
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 reviewing the existing C++ LLVM optimisation pass and the project’s current architecture. Define the scope and migration plan for a Rust rewrite, including how the pass’s behavior would be preserved; done would require an agreed design and a working Rust implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, rust
- Domain
- compilers
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100