GameState: Getter should not return references to types that implement Copy
Maintainers usually reply within 1 day
@NichtNil5 is already working on this.
Since Oct 6, 2026.
- #46 by @SturmEnte — closed without merging
Assessment
This issue has not been assessed yet.
Description
Why? @NichtNil5
- Dominant language
- Rust
- Stars
- 3
- Forks
- 1
- Avg merge
- 8h 33m
- Merged PRs (30d)
- 18
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from software-challenge/player_rust
-
Fix large enum variantPossibly taken @NichtNil5 claimed this 21 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
software-challenge/player_rust#22 · 1 assignee ·
Maintainers usually reply within 1 day
-
Message: Message should not wrap everything in OptionsPossibly taken @NichtNil5 claimed this 14 days ago. Open
software-challenge/player_rust#38 · 1 assignee ·
Maintainers usually reply within 1 day
-
Publishing workflow doesn't work because of branch protecitonPossibly taken @SturmEnte claimed this 15 days ago. Open
software-challenge/player_rust#35 · 1 assignee ·
Maintainers usually reply within 1 day
-
Error handling missingPossibly taken @NichtNil5 claimed this 20 days ago. Open
software-challenge/player_rust#24 · 1 comment · 2 assignees ·
Maintainers usually reply within 1 day
-
Documentation for developers and pupilsPossibly taken @NichtNil5 claimed this 14 days ago. Open
software-challenge/player_rust#8 · 7 comments · 2 assignees ·
Maintainers usually reply within 1 day
All issues in software-challenge/player_rust
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
metasequoiaime/msime#9113 ·
Maintainers usually reply within 1 day
-
area:desktop priority:p2 type:chore
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
area: supply-chain
Difficulty 1/5 Under an hour Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
-
Refresh stale docsOpen
Difficulty 1/5 1-3 hours Newbie friendliness 67/100
OpenCarControls/firmware#35 ·