OffsetArrays.jl VS StarWarsArrays.jl

Well, there is OffsetArrays in Julia, but it has acquired a reputation as a poison pill because most code assumes the 1-based indexing and it's easy to forget to convert the indexing and screw up the code.

Similar correctness issues are a big part of the reason that, several years ago, I submitted a series of pull requests to Julia so that its entire test suite would run without memory errors under Valgrind, save for a few that either (i) we understood and wrote suppressions for, or (ii) we did not understand and had open issues for. Unfortunately, no one ever integrated Valgrind into the CI system, so the test suite no longer fully runs under it, last time I checked. (The test suite took nearly a day to run under Valgrind on a fast desktop machine when it worked, so is infeasible for every pull request, but could be done periodically, e.g. once every few days.)

Even a revived effort on getting core Julia tests to pass under Valgrind would not do much to help catch correctness bugs due to composing different packages in the ecosystem. For that, running in testing with `--check-bounds=yes` is probably a better solution, and much quicker to execute as well. (see e.g. https://github.com/JuliaArrays/OffsetArrays.jl/issues/282)

You might be interested in OffsetArrays.jl.

Counting starts at one, as do most vector/matrix/tensor indices. If it bothers you too much, see OffsetArrays.jl and Arrays with custom indices.

No need for another version, Julia supports custom indices by default. Check out https://docs.julialang.org/en/v1/devdocs/offset-arrays/ and https://github.com/JuliaArrays/OffsetArrays.jl

I raise you https://github.com/giordano/StarWarsArrays.jl

Why not Star Wars Indices (4,5,6,1,2,3,7,8,9...)? https://github.com/giordano/StarWarsArrays.jl

> The documentation disagrees about string indices not starting with 1 As priorly said, I'm speaking about strings, not `String` in particular. So, to write code which work for all AbstractString (which have basic string functions), you must not assume that the first indexing is 1, you can have degenerate cases such as : https://github.com/giordano/StarWarsArrays.jl (this is for vectors, but creating a similar type, for AbstractString isn't impossible) or just strings with an offset indexing.

There are other choices like https://github.com/simonster/TwoBasedIndexing.jl and https://github.com/giordano/StarWarsArrays.jl if you do not like 1-based indexing.

This is a total non issue as indexing is an operation that is subject to multiple dispatch. For a humorous example see https://github.com/giordano/StarWarsArrays.jl

The cool thing with Julia is that array indices aren't inherent properties, and may be changed locally by using appropriate wrappers. This means that the same underlying array may start at 0 in one part of the code, at 1 in another, and perhaps use the star-wars indexing in yet another section if that's necessary.

Adding https://github.com/giordano/StarWarsArrays.jl to the list for some extra spice

You should also check out https://github.com/giordano/StarWarsArrays.jl and https://github.com/giordano/RandomBasedArrays.jl