Mitchell Hashimoto 4ef2240618 cli: parseCLI for optionals should not be null in release modes
Fixes #2747

I admit I don't fully understand this. But somehow, doing `var x: ?T =
undefined` in release fast mode makes `x` act as if its unset. I am
guessing since undefined does nothing to the memory, the memory layout
is such that it looks null for zeroed stack memory. This is a guess.

To fix this, I now initialize the type `T` and set it onto the optional
later. This commit also fixes an issue where calling `parseCLI` multiple
times on an optional would not modify the previous value if set.
2024-11-20 19:05:52 -08:00
..
2024-03-26 16:14:25 -07:00
2024-11-06 09:59:10 +01:00
2024-08-16 10:49:37 -07:00
2024-08-16 10:57:19 -07:00
2024-06-24 15:16:24 -07:00
2024-09-26 22:00:11 -07:00
2024-10-18 08:11:11 -07:00
2024-08-31 11:12:40 -07:00
2024-02-09 20:05:11 +01:00
2024-10-08 21:55:00 -07:00
2024-08-16 14:35:10 -07:00
2022-08-18 11:42:32 -07:00
2024-08-16 10:36:10 -07:00