annoying numpy promotion to int64 #117

New Issue

sb10q · 2021-11-28T12:16:04+08:00

sb10q commented

2021-11-28 12:16:04 +08:00

>>> x = 3
>>> x |= int32(8)
>>> type(x)
<class 'numpy.int64'>

Workaround:

>>> x = int32(3)
>>> x |= int32(8)
>>> type(x)
<class 'numpy.int32'>

There's probably nothing we can do about it, except document this pitfall which can cause surprising problems when writing @portable functions.

``` >>> x = 3 >>> x |= int32(8) >>> type(x) <class 'numpy.int64'> ``` Workaround: ``` >>> x = int32(3) >>> x |= int32(8) >>> type(x) <class 'numpy.int32'> ``` There's probably nothing we can do about it, except document this pitfall which can cause surprising problems when writing ``@portable`` functions.

sb10q added the

low-priority

label 2021-11-28 12:16:04 +08:00

sb10q referenced this issue

2022-04-12 11:05:36 +08:00

write user manual #58

sb10q added this to the Beta milestone 2022-04-12 11:05:41 +08:00

mwojcik referenced this issue

2022-04-26 17:26:19 +08:00

Phaser: "Call parameter does not match function signature!" #276

Sign in to join this conversation.