Skip to content

Commit a5c08c4

Browse files
authored
Removing wrong remark from Implementation section (#36083)
See also [this post](https://discourse.julialang.org/t/wrong-use-of-asymptotic-notation-in-the-multi-dimensional-arrays-page/40464?u=mathematics) in the community forum.
1 parent 2ab654c commit a5c08c4

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

doc/src/manual/arrays.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -969,7 +969,7 @@ be quite different from conventional arrays. For example, elements might be comp
969969
rather than stored. However, any concrete `AbstractArray{T,N}` type should generally implement
970970
at least [`size(A)`](@ref) (returning an `Int` tuple), [`getindex(A,i)`](@ref) and [`getindex(A,i1,...,iN)`](@ref getindex);
971971
mutable arrays should also implement [`setindex!`](@ref). It is recommended that these operations
972-
have nearly constant time complexity, or technically Õ(1) complexity, as otherwise some array
972+
have nearly constant time complexity, as otherwise some array
973973
functions may be unexpectedly slow. Concrete types should also typically provide a [`similar(A,T=eltype(A),dims=size(A))`](@ref)
974974
method, which is used to allocate a similar array for [`copy`](@ref) and other out-of-place
975975
operations. No matter how an `AbstractArray{T,N}` is represented internally, `T` is the type of

0 commit comments

Comments
 (0)