swift -help
reports options not available for all swift
subcommands without distinguishing them.
#68628
Labels
bug
A deviation from expected or documented behavior. Also: expected but undesirable behavior.
triage needed
This issue needs more specific labels
For example,
-working-directory
looks really promising for being able to invokeswift run
on a package from outside its working copy. In fact, no dice: if you put the option beforerun
thenrun
is interpreted as the name of a swift file. If you put it after, you getMost tools that have subcommands have a list of universal options and then options for specific commands, and they make the distinction clear in the help. I realize swift is a little different as you want to be able to say
swift SomeFile.swift
with no command. Maybe you could say there's an implicit commandrun-script
when the thing that would otherwise be a command name has a.swift
extension.The text was updated successfully, but these errors were encountered: