Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add range-checking to Buffer objects in Python #7128

Merged
merged 1 commit into from
Oct 27, 2022

Conversation

steven-johnson
Copy link
Contributor

using () to get or set a Buffer element wasn't being checked at runtime for Python, but it clearly should be, because Python. (Note that in C++ we don't always range-check for these operations -- it's limited to assert() checks -- but in Python the expectations are clearly different.)

using () to get or set a Buffer element wasn't being checked at runtime for Python, but it clearly should be, because Python. (Note that in C++ we don't always range-check for these operations -- it's limited to `assert()` checks -- but in Python the expectations are clearly different.)
@steven-johnson steven-johnson merged commit 48345d9 into main Oct 27, 2022
@steven-johnson steven-johnson deleted the srj/buf-bounds-check branch October 27, 2022 02:22
steven-johnson added a commit that referenced this pull request Oct 28, 2022
using () to get or set a Buffer element wasn't being checked at runtime for Python, but it clearly should be, because Python. (Note that in C++ we don't always range-check for these operations -- it's limited to `assert()` checks -- but in Python the expectations are clearly different.)
steven-johnson added a commit that referenced this pull request Oct 28, 2022
* Require Python 3.8+ in CMake build (#7117)
* Add range-checking to Buffer objects in Python (#7128)
* Fix Python buffer handling (#7125)
* add 'reverse_axes' options to Buffer conversions (#7127)
ardier pushed a commit to ardier/Halide-mutation that referenced this pull request Mar 3, 2024
using () to get or set a Buffer element wasn't being checked at runtime for Python, but it clearly should be, because Python. (Note that in C++ we don't always range-check for these operations -- it's limited to `assert()` checks -- but in Python the expectations are clearly different.)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants