Add unwind kinds and a "default unwind kind" method?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by locating the existing CallingConvention enum and default_calling_convention() method. Read how calling conventions are represented and used, then investigate whether unwind kind is implied or needs an independent API. Done means reaching a documented design decision about UnwindKind and default_unwind_kind().
Written by the indexing model from the issue text.
Description
Similar to the CallingConvention enum and the default_calling_convention() method, should we add an UnwindKind enum and default_unwind_kind() method?
One question is, do we need this, or should the unwind kind be implied by the calling convention?
- Dominant language
- Rust
- Stars
- 61
- Forks
- 72
- PR merge metrics
- No merged PRs in 30d
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 bytecodealliance/target-lexicon
-
Remove build script?Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
bytecodealliance/target-lexicon#112 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
bytecodealliance/target-lexicon#78 · 4 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
bytecodealliance/target-lexicon#76 · 7 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
bytecodealliance/target-lexicon#63 · 3 comments ·
All issues in bytecodealliance/target-lexicon
Similar issues
-
area:config area:security bug good first issue platform:linux platform:windows priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
documentation P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
vllm-project/agentic-api#463 ·
Maintainers usually reply within 2 days
-
bug good first issue priority:high
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Konfirm-xyz/konfirm-contracts#163 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day