"Implicit conversion changes signedness" warning from unicodeobject.h
Open
Nobody has claimed this yet.
good first issue
- Dominant language
- Python
- Stars
- 1.6k
- Forks
- 155
- Avg merge
- 9h 42m
- Merged PRs (30d)
- 36
Description
The GraalVM declares PyUnicode_KIND as
enum PyUnicode_Kind {
/* Return values of the PyUnicode_KIND() function: */
PyUnicode_1BYTE_KIND = 1,
PyUnicode_2BYTE_KIND = 2,
PyUnicode_4BYTE_KIND = 4
};
while Python C-API:
PyAPI_FUNC(int) PyUnicode_KIND(PyObject *op);
Contributor guide
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
Start by comparing GraalVM's PyUnicode_KIND declaration with the Python C-API declaration shown in the issue and reproduce the signedness warning. Determine which declaration should match the other, then verify that the warning is resolved without breaking the related Unicode C-API behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, java, python
- Domain
- backend, compilers
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100