Integer core configuration field
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reviewing the libretro-common interfaces used for custom core configuration and identify how existing configuration fields are represented. Determine whether integer fields are supported, what API change would be required if they are not, and define a testable completion condition for specifying and reading one.
Written by the indexing model from the issue text.
Description
Is it possible to specify any integer configuration fields in custom cores?
- Dominant language
- C
- Stars
- 180
- Forks
- 99
- Avg merge
- 7h 16m
- Merged PRs (30d)
- 1
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 libretro/libretro-common
-
linked_list remove-matching functions crash on a NULL callbackPossibly taken @Awesome-00 claimed this 12 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
libretro/libretro-common#232 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
libretro/libretro-common#220 · 1 comment · 1 reaction ·
-
RETRO_ENVIRONMENT_ clash in libretro.hPossibly taken @Clownacy claimed this 27 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
libretro/libretro-common#89 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
libretro/libretro-common#223 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
libretro/libretro-common#221 · 1 reaction ·
All issues in libretro/libretro-common
Similar issues
-
Policy query leaks host primary block (BSL_PrimaryBlock_deinit skipped) on two early-exit pathsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
NASA-AMMOS/BSL#355 ·
Maintainers usually reply within 1 day
-
#242 leftovers: dated narrative and shas in the social-features test planPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
EchoTools/nevr-runtime#264 ·
Maintainers usually reply within 1 day
-
area/docdb kind/bug priority/medium status/awaiting-triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
yugabyte/yugabyte-db#34873 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
category:port-update
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days