INDAPlus21 / INDAPlus21/osveijer-task-13
Pass
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Very well done Oliver!
It's not often I come over this message, but you did it(!):
PS C:\Users\viola\Documents\INDA_2021\tasks\plus-task-13\osveijer\osveijer-task-13> cargo run
[...]
Compiling osveijer-task-13 v0.1.0 (C:\Users\viola\Documents\INDA_2021\tasks\plus-task-13\osveijer\osveijer-task-13)
Finished dev [unoptimized + debuginfo] target(s) in 9.55s
Running `target\debug\osveijer-task-13.exe`
thread 'main' has overflowed its stack
error: process didn't exit successfully: `target\debug\osveijer-task-13.exe` (exit code: 0xc00000fd, STATUS_STACK_OVERFLOW)
Lucky you that the release version doesn't have that issue.
Rust goldstar to you. However, I do wish for some modularity to ease navigation, in addition to documentation to ease understanding. Documentation further enables you to referens this project in the future. This is a flex piece after all.
Keep it up!
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
The issue names no files, tests, or entry points. Start by reviewing the repository structure and defining the requested modularity and documentation scope with the maintainer. Done means the project is easier to navigate and understand, with documentation covering its purpose and usage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- developer-experience, documentation
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100