may_share_memory(a, b, /, max_work=None)
A return of True does not necessarily mean that the two arrays share any element. It just means that they might.
Only the memory bounds of a and b are checked by default.
Input arrays
Effort to spend on solving the overlap problem. See shares_memory
for details. Default for may_share_memory
is to do a bounds check.
Determine if two arrays might share memory
>>> np.may_share_memory(np.array([1,2]), np.array([5,8,9])) False
>>> x = np.zeros([3, 4])See :
... np.may_share_memory(x[:,0], x[:,1]) True
The following pages refer to to this document either explicitly or contain code examples using this.
numpy.core._multiarray_umath.shares_memory
numpy.shares_memory
Hover to see nodes names; edges to Self not shown, Caped at 50 nodes.
Using a canvas is more power efficient and can get hundred of nodes ; but does not allow hyperlinks; , arrows or text (beyond on hover)
SVG is more flexible but power hungry; and does not scale well to 50 + nodes.
All aboves nodes referred to, (or are referred from) current nodes; Edges from Self to other have been omitted (or all nodes would be connected to the central node "self" which is not useful). Nodes are colored by the library they belong to, and scaled with the number of references pointing them