That's only, like, half the problem.

It's an array of string parameters.

No semantics! Just an variety of customs about what it means when a parameters begins with a - or a -- or if you have -- by itself preceding some characters, how to break lists of arguments with separators, what happens when you pass the same argument twice, etc etc etc.

To choose the worst possible solution better than that, we could instead be passing in a single string with a JSON dictionary that says things like '{ "recursive": True, "force": True, "files": [ "file1", "file2", "file3" ]}'

The irony is that I’ve had to add shell word splitting into in my real programming language code because of how many people prefer

    run(f”command {arg} -v -p{opt} {target}”)

to

    run([“command”, arg, “-v”, “-p”, opt, target])

FWIW bash supports arrays, and running commands with an array providing the arguments