Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Should `cython.declare`, `cython.pointer` and so on be strictly considered not `in_c_type_context`?

See original GitHub issue

Should cython.declare, cython.pointer and so on be strictly considered not in_c_type_context? At least for .py files?

_Originally posted by @0dminnimda in https://github.com/cython/cython/issues/4606#issuecomment-1179806535_

Issue Analytics

State:
Created a year ago
Comments:5 (4 by maintainers)

Top GitHub Comments

1reaction

scodercommented, Jul 16, 2022

I agree with @da-woods that the main distinction point is currently user intent, and we should leave it at that. ISTM that cython.declare(int) now interprets int as C int, which is the intended behaviour. I added a test. https://github.com/cython/cython/commit/6414a07ec88b60d604daf0e51fd850ee974afdcb

0reactions

0dminnimdacommented, Jul 11, 2022

I argue that cython.declare(cython.pointer(cython.double)) == cython.declare(cython.pointer(float)) But I can see that both interpretations can lead to misunderstandings and unexpected behaviour. Now it’s about what will cause less of it