Are the integers really signed or unsigned?
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
Research direction
Compare the parameter definitions at src/lib.rs line 2 and Main.lean line 2, then trace how the Rust FFI boundary represents and passes the values. Determine whether the signedness mismatch is intentional or a bug; done means the issue has a documented resolution and the definitions are consistent if a change is required.
Written by the indexing model from the issue text.
Description
Rust code defines the parameters to be signed i32:
https://github.com/lurk-lab/RustFFI.lean/blob/af3a8f68d1657d4db9cac43e9bbba0bec1aaf1ad/src/lib.rs#L2
But Lean defines them to be unsigned UInt32:
https://github.com/lurk-lab/RustFFI.lean/blob/af3a8f68d1657d4db9cac43e9bbba0bec1aaf1ad/Main.lean#L2
How does that even work 🤯
- Dominant language
- Lean
- Stars
- 17
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
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.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
internal.h中，漏掉了1个定义。 Open
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
oxc-project/oxc#26944 ·