Added a default to the name parameter

[rmonnet]

In Odin, the solution stub generates a compilation error rather than a failed test. This is confusing to the student and contrary to the philosophy we use for the other exercises. I added a zero value default to the parameter to convert the compile error to a failed test. Since this is the only exercise where we have to define a default parameter, I added Odin specific instructions explaining how to use default parameters in Odin.

[glennj]

I think the doc gives the "how" but is missing the "what and why". Something like

The parameter list of a procedure declares the type or each parameter.
The caller of a procedure must supply values to assign to each of the parameters.
To allow some flexibility, Odin can provide a default value to a parameter so the caller does not have to explicitly provide a value.

That's crap, my brain is not fully engaged this morning.

Maybe linking to https://odin-lang.org/docs/overview/#parameters

[glennj]

Google Gemini gave me this which is still not great.

In a strongly-typed language like Odin, default parameters improve usability by reducing repetitive code and allowing for non-breaking API updates. This feature doesn't compromise type safety, as the compiler simply substitutes the default when a value is omitted, ensuring the function always receives a value of the correct type.

[rmonnet]

@glennj,

good point. I rewrote the additional instructions using your comments above. I found that, once I try to explain the why, I had to discuss procedure overloading and named arguments. Once we start the concept track, we may need a concept on this specific topic.

Let me know what you think of the updated doc.

[glennj]

Nice!

Link to docs?

[named-arguments]: https://odin-lang.org/docs/overview/#named-arguments
[default-values]: https://odin-lang.org/docs/overview/#default-values

[rmonnet]

Added a link to the Odin overview as suggested.