However, I'd treat outputs as lists so one could also split an array like this:
[ 1 2 ]
The splitting and combination syntax is kinda a headache in general, and i think we should on a type level only allow single inputs and outputs in an operator/command/modifier (though, of course…
What is missing before we could merge this? Basically every PR currently made depends on this.
Since the default is false which is also returned by `bool::default, the extra function is not necessary:
If there's no config file, should we fall back to defaults?
Yes, imo. Allows trying out iowo quickly without actually leaving permanent traces.
What if we have one, but reading it…
Nevermind, I misinterpreted now_utc. I thought it'd return the current system time and assume it to be UTC, but it doesn't:
>> :dep time = { features = ["local-offset"] }
Compiling…In the current stage of the project, there isn't. But functions are something that, IMO should be definable by users (in the language), so maybe instructions may just be a subset of functions,…
I found no fitting AST repr for the source code we're heading for atm. Though you're invited to share your thoughts on how one might look like.
Yeah, after pushing the branch to your fork, you can use the Edit button at the top of this page to make the PR source and target configurable.
Can always use now_utc, since no calculations are performed based on the timezone.
Might want to streamline those two, in order to avoid accidentally checking only one of them in future.
Maybe report_serde_err could take a custom error, which the errors from ron and serde_json are converted into.