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

Meaning of type parameters for Arrays is not discoverable #19211

Closed
dpsanders opened this issue Nov 3, 2016 · 3 comments · Fixed by #22052
Closed

Meaning of type parameters for Arrays is not discoverable #19211

dpsanders opened this issue Nov 3, 2016 · 3 comments · Fixed by #22052
Labels
docs This change adds or pertains to documentation

Comments

@dpsanders
Copy link
Contributor

As pointed out by @alanedelman:

While typing AbstractArray indicates that there are two type parameters,
neither ?AbstractArray nor ?Array give information about what those parameters are for.

This also seems to be difficult to discover from http://docs.julialang.org/en/release-0.5/manual/arrays/

@tkelman tkelman added the docs This change adds or pertains to documentation label Nov 4, 2016
@fredrikekre
Copy link
Member

Considered fixed?

help?> Array
search: Array SubArray BitArray ConjArray DenseArray StridedArray PermutedDimsArray SharedArray SparseArrays takebuf_array AbstractArray AbstractSparseArray CartesianRange searchsortedlast AbstractSerializer

  Array{T}(dims)
  Array{T,N}(dims)

  Construct an uninitialized N-dimensional dense array with element type T, where N is determined from the length or number of dims. dims may be a tuple or a series of integer arguments corresponding to the
  lengths in each dimension. If the rank N is supplied explicitly as in Array{T,N}(dims), then it must match the length or number of dims.

@dpsanders
Copy link
Contributor Author

Yes, thanks.

@dpsanders
Copy link
Contributor Author

A couple of examples in the help text would be nice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs This change adds or pertains to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants