updated ellipsis chars

[artkuo]

As discussed in #8593, here are changes to documentation to use midline ellipsis ⋯ to refer to etc., to distinguish from the splice notation ... (three periods in a row). It was confusing because the same string of characters had two different meanings, which could only be distinguished by guessing the author's intent. I believe that ⋯ was intended in the majority of cases, and I have attempted to preserve explicit correct use of splice (...) where appropriate.

I am new to Julia. I would appreciate if someone could look through all of the many changes to verify their correctness.

[StefanKarpinski]

Thanks for doing this – I'm sure we can hall get this done in short order.

[Keno]

These could arguably be correct as is.

[artkuo]

I thought about that for a while, and I'm still not sure, but my reasoning is this:

1. First thing worth learning is probably something like Array(Float64, 1) or Array(Float64, 1, 2)
2. Array also accepts a tuple like Array(Float64, (1, 2)) as the text above says
3. There's no need to splat a tuple like Array(Float64, (1,2)...) which is the same as syntax 2
4. You can splat an array like Array(Float64, [1, 2]...) which doesn't work without the ... but I would consider this to be a less-used case. And if you understand syntax 1 and you (separately) learn about splatting/splicing, then this one is automatic

Of course, I can't get into the mind of the original author. The most difficult cases for me were ones like this, which perhaps should be written with a comma such as Array(type, dim, ⋯) to reduce ambiguity. But the fact that it's ambiguous is all the more reason why it should be clarified one way or another.

[JeffBezanson]

Um, this seems to have deleted the entire repository?

[quinnj]

I always wondered what a PR would look like to need a "Lock Pull Request" feature. :)

[ivarne]

As long as you don't have push access (and nobody merges your PR), there is nothing wrong you can do (except creating noise). As this PR stands, merging it will delete all files in the Julia repository, which is obviously not good, and probably why @StefanKarpinski closed the PR.

We're usually pretty helpful if you have trouble with git, especially if you have read a few tutorials you have specific questions/problems. This PR is from your master branch, which is generally regarded as bad praxis, because it often causes trouble. At this point you should probably do a full reset, on your local git repository, and do your changes from a fresh start.

git reset --hard origin/master
git checkout -b doc_fixes
# do your changes
git add doc/...
git commit
git push fork doc_fixes

(I have assumed that you have the official repo as the origin remote, and your fork as fork)