type. "Fast" arrays like NumPy arrays that store elements in-place (i.e., dtype is np.float64, [('f1', np.uint64), ('f2', np.int32)], etc.) can be rep- resented by Array{T} where T is a concrete, immutable Musical Keyboard U+1F3BA \:trumpet: Trumpet U+1F3BB \:violin: Violin U+1F3BC \:musical_score: Musical Score U+1F3BD \:run- ning_shirt_with_sash: Running Shirt With Sash U+1F3BE \:tennis: Tennis states that calling with certain argtypes is a part of public API. For example, the change between f1 and f2 in the example below is usually considered compatible because the change is invisible by the

type. "Fast" arrays like NumPy arrays that store elements in-place (i.e., dtype is np.float64, [('f1', np.uint64), ('f2', np.int32)], etc.) can be rep- resented by Array{T} where T is a concrete, immutable Musical Keyboard U+1F3BA \:trumpet: Trumpet U+1F3BB \:violin: Violin U+1F3BC \:musical_score: Musical Score U+1F3BD \:run- ning_shirt_with_sash: Running Shirt With Sash U+1F3BE \:tennis: Tennis states that calling with certain argtypes is a part of public API. For example, the change between f1 and f2 in the example below is usually considered compatible because the change is invisible by the

type. "Fast" arrays like NumPy arrays that store elements in-place (i.e., dtype is np.float64, [('f1', np.uint64), ('f2', np.int32)], etc.) can be rep- resented by Array{T} where T is a concrete, immutable Musical Keyboard U+1F3BA \:trumpet: Trumpet U+1F3BB \:violin: Violin U+1F3BC \:musical_score: Musical Score U+1F3BD \:run- ning_shirt_with_sash: Running Shirt With Sash U+1F3BE \:tennis: Tennis states that calling with certain argtypes is a part of public API. For example, the change between f1 and f2 in the example below is usually considered compatible because the change is invisible by the

type. "Fast" arrays like NumPy arrays that store elements in-place (i.e., dtype is np.float64, [('f1', np.uint64), ('f2', np.int32)], etc.) can be rep- resented by Array{T} where T is a concrete, immutable Musical Keyboard U+1F3BA \:trumpet: Trumpet U+1F3BB \:violin: Violin U+1F3BC \:musical_score: Musical Score U+1F3BD \:run- ning_shirt_with_sash: Running Shirt With Sash U+1F3BE \:tennis: Tennis states that calling with certain argtypes is a part of public API. For example, the change between f1 and f2 in the example below is usually considered compatible because the change is invisible by the

type. "Fast" arrays like NumPy arrays that store elements in-place (i.e., dtype is np.float64, [('f1', np.uint64), ('f2', np.int32)], etc.) can be rep- resented by Array{T} where T is a concrete, immutable Musical Keyboard U+1F3BA \:trumpet: Trumpet U+1F3BB \:violin: Violin U+1F3BC \:musical_score: Musical Score U+1F3BD \:run- ning_shirt_with_sash: Running Shirt With Sash U+1F3BE \:tennis: Tennis states that calling with certain argtypes is a part of public API. For example, the change between f1 and f2 in the example below is usually considered compatible because the change is invisible by the

type. "Fast" arrays like NumPy arrays that store elements in-place (i.e., dtype is np.float64, [('f1', np.uint64), ('f2', np.int32)], etc.) can be rep- resented by Array{T} where T is a concrete, immutable Musical Keyboard U+1F3BA \:trumpet: Trumpet U+1F3BB \:violin: Violin U+1F3BC \:musical_score: Musical Score U+1F3BD \:run- ning_shirt_with_sash: Running Shirt With Sash U+1F3BE \:tennis: Tennis states that calling with certain argtypes is a part of public API. For example, the change between f1 and f2 in the example below is usually considered compatible because the change is invisible by the

type. "Fast" arrays like NumPy arrays that store elements in-place (i.e., dtype is np.float64, [('f1', np.uint64), ('f2', np.int32)], etc.) can be rep- resented by Array{T} where T is a concrete, immutable Musical Keyboard U+1F3BA \:trumpet: Trumpet U+1F3BB \:violin: Violin U+1F3BC \:musical_score: Musical Score U+1F3BD \:run- ning_shirt_with_sash: Running Shirt With Sash U+1F3BE \:tennis: Tennis states that calling with certain argtypes is a part of public API. For example, the change between f1 and f2 in the example below is usually considered compatible because the change is invisible by the

type. "Fast" arrays like NumPy arrays that store elements in-place (i.e., dtype is np.float64, [('f1', np.uint64), ('f2', np.int32)], etc.) can be rep- resented by Array{T} where T is a concrete, immutable Musical Keyboard U+1F3BA \:trumpet: Trumpet U+1F3BB \:violin: Violin U+1F3BC \:musical_score: Musical Score U+1F3BD \:run- ning_shirt_with_sash: Running Shirt With Sash U+1F3BE \:tennis: Tennis states that calling with certain argtypes is a part of public API. For example, the change between f1 and f2 in the example below is usually considered compatible because the change is invisible by the

type. "Fast" arrays like NumPy arrays that store elements in-place (i.e., dtype is np.float64, [('f1', np.uint64), ('f2', np.int32)], etc.) can be rep- resented by Array{T} where T is a concrete, immutable Musical Keyboard U+1F3BA \:trumpet: Trumpet U+1F3BB \:violin: Violin U+1F3BC \:musical_score: Musical Score U+1F3BD \:run- ning_shirt_with_sash: Running Shirt With Sash U+1F3BE \:tennis: Tennis states that calling with certain argtypes is a part of public API. For example, the change between f1 and f2 in the example below is usually considered compatible because the change is invisible by the

type. "Fast" arrays like NumPy arrays that store elements in-place (i.e., dtype is np.float64, [('f1', np.uint64), ('f2', np.int32)], etc.) can be rep- resented by Array{T} where T is a concrete, immutable Musical Keyboard U+1F3BA \:trumpet: Trumpet U+1F3BB \:violin: Violin U+1F3BC \:musical_score: Musical Score U+1F3BD \:run- ning_shirt_with_sash: Running Shirt With Sash U+1F3BE \:tennis: Tennis states that calling with certain argtypes is a part of public API. For example, the change between f1 and f2 in the example below is usually considered compatible because the change is invisible by the