(Sorry for the ridiculous rate of release, again, but...) On the topic of memory safety, PyQrack fundamentally can't hide "unsafe code" from the user code namespace, should a user be inclined to invoke it. However, for wrapped calls to the shared library interface, we can at least check that the raw pointer array arguments sent to the shared library cannot possibly cause segmentation faults.
When a numerical list argument of insufficient length is passed to the wrapper API, PyQrack will now raise a `ValueException`, to protect users from accidentally inducing segmentation faults.
File SHA-1 sums:
37e1e898f8250e11ef91429b482de98de19e7d75 pyqrack-1.11.3-py3-none-any.whl
2417af5e6e0eeae5b21b64137b46c64aebae9814 pyqrack-1.11.3-py3-none-linux_aarch64.whl
00f3c4e1b8da84be742b35415536ba0907aa8060 pyqrack-1.11.3-py3-none-linux_armv7l.whl
43df5a7953e83e1f4dea14ec4c28787448787e83 pyqrack-1.11.3-py3-none-macosx_10_4_x86_64.whl
fa89243cec34799be002e1509be93930930e410b pyqrack-1.11.3-py3-none-manylinux2014_x86_64.whl
f66b5da63528de86918616bba878692db3ea4989 pyqrack-1.11.3-py3-none-manylinux_2_35_x86_64.whl
1810cbc245fa607f78899e8fa409fd94f8fb7b60 pyqrack-1.11.3-py3-none-win32.whl
0483eee07b41a55c1c0d673bb430c52ac316e4d7 pyqrack-1.11.3-py3-none-win_amd64.whl
d7a8065ca703b34a08299e0195496dbe9b0b5ef7 pyqrack-1.11.3.tar.gz