Add an example with automatic array size

[adriancuadrado]

You can learn more about this here: https://go.dev/blog/slices-intro#arrays

[eliben]

Nice, thank you! Some comments before we proceed

[eliben]

This comment is a good place to add that the array length is the maximum index plus one

[adriancuadrado]

I don't think that information would add much value since gobyexample is meant for people who already have experience in other programming languages and the length of a list is always the maximum index plus one everywhere.

[eliben]

Right, I mean it specifically in the context of the [...] syntax with explicitly specifying indeces. For example in your second b with the 3:, the array length is 5 because of that.

I don't feel strongly about this, though.

[adriancuadrado]

I've noticed a file called arrays.hash. What is that for? Do I also have to update it?

[eliben]

I've noticed a file called arrays.hash. What is that for? Do I also have to update it?

You don't need to do it manually, you should run tools/build which will also generate the public HTML for you. Did you do that for this PR?

[adriancuadrado]

@eliben

I've noticed a file called arrays.hash. What is that for? Do I also have to update it?

You don't need to do it manually, you should run tools/build which will also generate the public HTML for you. Did you do that for this PR?

I assumed these kind of things were made automatically by a CI/CD pipeline of some sort, as most people do. I'll run the script and commit the result, but I think you should consider creating a Github Action workflow or something instead.

---

EDIT: Hold on, you actually have that, but you use it to test the result and make sure I ran the script. Why though? Can't you just use the result of running that script automatically instead?

[eliben]

I assumed these kind of things were made automatically by a CI/CD pipeline of some sort, as most people do. I'll run the script and commit the result, but I think you should consider creating a Github Action workflow or something instead.

EDIT: Hold on, you actually have that, but you use it to test the result and make sure I ran the script. Why though? Can't you just use the result of running that script automatically instead?

The output in public is currently committed to the repository, because the deployment process is a simple upload to a bucket. I want to keep the CI process simple - don't want it to change PRs/commits - it's only there to verify that everything was done correctly. Running tools/build locally is important for testing the output anyway, so this isn't a problem in reality