Read-only array exchange via the buffer protocol #217
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adapts nanobind so that it can both receive and return arrays representing read-only memory. This is communicated via the standard
const
type modifier, e.g. by replacingnb::ndarray<float, ...>
withnb::ndarray<const float, ...>
.The PR also adapts accessors (
data()
,operator()
) so that they only return constant references/pointers in that case.The change is for now specific to the buffer protocol used to exchange nd-arrays with NumPy. The DLPack interface (used to exchange nd-arrays with PyTorch, Tensorflow, etc.) ignores the read-only annotation. This may change at some point in the future when an upcoming DLPack version with a read-only bit is more widely deployed.
This PR only targets the
ndarray
class. It will be nice to also propagate it into the Eigen type caster (@WKarel ?)