JalonSolov

I also think this _should_ work. Similar thing was fixed in `match` recently... basically the same issue.

It should work because it is short-circuiting the program flow such that `var` doesn't _need_ to be defined - it is exiting that code flow and returning to the caller.

:man_shrugging:

"typically"... where? :-) I've seen error logs go to stderr, but regular log messages often go to stdout. It would, however, be nice to have the choice.

This is a case of V's default initialization combined with no constructors, is causing a problem. The key is in the output: `unix: 0000000` for your initial Time. `add_days` adds...

Well, no, it will just pass those complicated structs on the stack. You only need to change the code if you _want_ them to be passed as references, instead of...

Or, in other words, it will always be "pass by value" now, instead of sometimes pass by value, and sometimes pass by reference. If you want pass by reference, you...

Any thoughts on finishing this one?

`fn (f Foo)` would be pass by value, since it wouldn't be modifiable. `fn (mut f Foo)` or `fn (&f foo)` would be pass by reference.

Yeah, I've always been against it. Compilers _should_ make things easier, instead of propagating the same silliness as always. V should be able to figure out when the `&` is...