JalonSolov

Or, to match the request... ```v type Arg = f32 | int | Person | string fn Hello(args ...Arg) {} ```

Personally, I would like for it to warn about options after the filename. This is one way `v build` is different from `v run`. In `v run`, all options after...

Try `v up`. It works for me on Manjaro with latest V: ``` ... 6478007018 :24880 2766336227 :24890 9781045463 :24900 3113129404 :24910 4833570134 :24920 8695851652 :24930 6745951518 :24940 7680033395 :24950...

Latest V is `V 0.4.5 a1497c0`. Your version is from 3 weeks ago, and is 132 commits behind the current. Since V is still changing often, it is always best...

That screenshot is too dark for me to read, so I'm not sure what you're saying is the problem, there.

How much RAM do you have? I did start it with the higher number, and let it run for a couple of hours... still no output. So I checked free...

We recommend installing gcc/clang from https://winlibs.com rather than using the msys install.

This is why pointers are so fraught... Yes, `rere` returns an immutable pointer... to a struct with a mutable field. Modifying that field is perfectly valid.

It's not a "feature", per se... it is simply the way things work, IMO.

However, the code here isn't modifying `User` or `&User`. It is only modifying the mutable field inside `User`. That's why I said it is the way things work. Creating an...