I agree with David--building before running is the most sensible default, both because of precedent and because it is, by construction, the most common scenario. I would be highly surprised if a _build_ tool offered to run stale code by default without warning me.<br><div class="gmail_quote"><div dir="ltr">On Mon, May 15, 2017 at 05:45 Rien via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
> On 15 May 2017, at 11:58, David Hart <<a href="mailto:david@hartbit.com" target="_blank">david@hartbit.com</a>> wrote:<br>
><br>
>><br>
>> On 15 May 2017, at 10:40, Rien <<a href="mailto:Rien@balancingrock.nl" target="_blank">Rien@balancingrock.nl</a>> wrote:<br>
>><br>
>><br>
>>> On 15 May 2017, at 10:12, David Hart <<a href="mailto:david@hartbit.com" target="_blank">david@hartbit.com</a>> wrote:<br>
>>><br>
>>><br>
>>>> On 15 May 2017, at 10:03, Rien <<a href="mailto:Rien@balancingrock.nl" target="_blank">Rien@balancingrock.nl</a>> wrote:<br>
>>>><br>
>>>> I always wondered why it did not exist already ;-)<br>
>>>><br>
>>>> However, I am not sure if I like the “auto build” aspect. For example I may have started working on a change, but quickly want to verify the exact old behaviour. Then I want to run the old build again. While this proposal does not make this impossible, it makes it more cumbersome as I now need to remember when to use the old method and the new run command.<br>
>>><br>
>>> There is a —skip-build option to run without building. I think it’s better this way before (1) building before running seems like the most common scenario and (2) it mirrors how it works with swift test. Having it work the other way round for run would be very confusing IMHO.<br>
>><br>
>> To me this violates the “least surprising use” rule. (Same for ‘test’, even though it sets a precedence)<br>
>> Command line execution should either do as it says, or give an error message. This is quite different from a GUI behaviour: a GUI ‘run’ command should build if necessary - and indeed Xcode does just that)<br>
>> I think it’s a mistake to try to mimic GUI behaviour in a command line environment.<br>
><br>
> Firstly, there are other precedents. swift build itself will get dependencies if needed. In cargo, the closest equivalent to SwiftPM (i.e., a package manager/build tool for a language that needs a compilation stage) cargo run builds beforehand.<br>
><br>
> Secondly, if we agree that building before running is the most common scenario, why not make it the default?<br>
><br>
<br>
I am not familiar with Cargo.<br>
But pretty much any example you can site is something I dislike ;-)<br>
On the command line I like single-purpose commands since that makes creating and understanding scripts easier.<br>
Maybe that is just me…<br>
<br>
Rien.<br>
<br>
> David.<br>
><br>
>> Regards,<br>
>> Rien.<br>
>><br>
>>><br>
>>>> Having a build option would make more sense imo, i.e:<br>
>>>> $ swift run<br>
>>>> Always runs the present build<br>
>>>> $ swift run -b<br>
>>>> Builds first, then runs the new build.<br>
>>>><br>
>>>><br>
>>>> Regards,<br>
>>>> Rien<br>
>>>><br>
>>>> Site: <a href="http://balancingrock.nl" rel="noreferrer" target="_blank">http://balancingrock.nl</a><br>
>>>> Blog: <a href="http://swiftrien.blogspot.com" rel="noreferrer" target="_blank">http://swiftrien.blogspot.com</a><br>
>>>> Github: <a href="http://github.com/Balancingrock" rel="noreferrer" target="_blank">http://github.com/Balancingrock</a><br>
>>>> Project: <a href="http://swiftfire.nl" rel="noreferrer" target="_blank">http://swiftfire.nl</a> - A server for websites build in Swift<br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>><br>
>>>>> On 15 May 2017, at 09:47, David Hart via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br>
>>>>><br>
>>>>> Hello evolution (and build-dev),<br>
>>>>><br>
>>>>> I’d like to pitch a QOL proposal to improve the development of command-line Swift Packages by introducing a `swift run` command. I’d value any feedback before moving forward.<br>
>>>>><br>
>>>>> <a href="https://github.com/hartbit/swift-evolution/blob/swift-run-command/proposals/XXXX-swift-run-command.md" rel="noreferrer" target="_blank">https://github.com/hartbit/swift-evolution/blob/swift-run-command/proposals/XXXX-swift-run-command.md</a><br>
>>>>><br>
>>>>> Regards,<br>
>>>>> David.<br>
>>>>><br>
>>>>> Swift run Command<br>
>>>>><br>
>>>>> • Proposal: SE-XXXX<br>
>>>>> • Authors: David Hart<br>
>>>>> • Review Manager: TBD<br>
>>>>> • Status: TBD<br>
>>>>> Introduction<br>
>>>>><br>
>>>>> The proposal introduces a new swift run command to build and run an executable defined in the current package.<br>
>>>>><br>
>>>>> Motivation<br>
>>>>><br>
>>>>> It is common to want to build and run an executable during development. For now, one must first build it and then execute it from the build folder:<br>
>>>>><br>
>>>>> $ swift build<br>
>>>>> $ .build/debug/myexecutable<br>
>>>>><br>
>>>>> In Swift 4, the Swift Package Manager will build to a different path, containing a platform sub-folder (.build/macosx-x86_64/debug for mac and .build/linux-x86_64/debug for linux), making it more cumbersome to run the executable from the command line.<br>
>>>>><br>
>>>>> To improve the development workflow, the proposal suggest introducing a new first-level swift run command that will build if necessary and then run an executable defined in the Package.swift manifest, replacing the above steps into just one.<br>
>>>>><br>
>>>>> Proposed solution<br>
>>>>><br>
>>>>> The swift run command would be defined as:<br>
>>>>><br>
>>>>> $ swift run --help<br>
>>>>> OVERVIEW: Build and run executable<br>
>>>>><br>
>>>>> USAGE: swift run [options] [executable] [-- arguments]<br>
>>>>><br>
>>>>> OPTIONS:<br>
>>>>> --build-path Specify build/cache directory [default: ./.build]<br>
>>>>> --chdir, -C Change working directory before any other operation<br>
>>>>> --in-dir, -I Change working directory before running the executable<br>
>>>>> --color Specify color mode (auto<br>
>>>>> |always|<br>
>>>>> never) [default: auto]<br>
>>>>> --configuration, -c Build with configuration (debug<br>
>>>>> |<br>
>>>>> release) [default: debug]<br>
>>>>> --enable-prefetching Enable prefetching<br>
>>>>> in<br>
>>>>> resolver<br>
>>>>> --skip-build Skip building the executable product<br>
>>>>> --verbose, -v Increase verbosity of informational output<br>
>>>>> -Xcc Pass flag through to all C compiler invocations<br>
>>>>> -Xlinker Pass flag through to all linker invocations<br>
>>>>> -Xswiftc Pass flag through to all Swift compiler invocations<br>
>>>>> --help Display available options<br>
>>>>><br>
>>>>> If needed, the command will build the product before running it. As a result, it can be passed any options swift buildaccepts. As for swift test, it also accepts an extra --skip-build option to skip the build phase. A new --in-diroption is also introduced to run the executable from another directory.<br>
>>>>><br>
>>>>> After the options, the command optionally takes the name of an executable product defined in the Package.swiftmanifest and introduced in SE-0146. If called without an executable and the manifest defines one and only one executable product, it will default to running that one. In any other case, the command fails.<br>
>>>>><br>
>>>>> The executable can be called with arguments by prefixing them with a -- to separate them from the executable name.<br>
>>>>><br>
>>>>> Alternatives considered<br>
>>>>><br>
>>>>> One alternative to the Swift 4 change of build folder would be for the Swift Package Manager to create and update a symlink at .build/debug and .build/release that point to the latest build folder for that configuration. Although that should probably be done to retain backward-compatibility with tools that depended on the build location, it does not completely invalid the usefulness of the run command.<br>
>>>>> _______________________________________________<br>
>>>>> swift-evolution mailing list<br>
>>>>> <a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
>>>>> <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
<br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div>