[swift-build-dev] [swift-evolution] [Review] SE-0179: Swift `run` Command
david at hartbit.com
Tue May 16 09:15:23 CDT 2017
> On 16 May 2017, at 14:32, Gwendal Roué via swift-evolution <swift-evolution at swift.org> wrote:
>> Le 16 mai 2017 à 02:09, Daniel Dunbar via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> a écrit :
>> Hello Swift community,
>> The review of SE-0179: Swift `run` Command begins now and runs through May 25th, 2017.
>> The proposal is available here:
>> https://github.com/apple/swift-evolution/blob/master/proposals/0179-swift-run-command.md <https://github.com/apple/swift-evolution/blob/master/proposals/0179-swift-run-command.md>
>> What is your evaluation of the proposal?
> Good +1
> It's not quite clear if `swift run --configuration release` runs the release build, but I'll assume it's true.
It’s true. Same behaviour as with swift test.
> The considered alternative of symlinking to the latest build folder looks like an opportunity for bugs, as most stateful command-line interfaces: I'm not in favor for it.
>> Is the problem being addressed significant enough to warrant a change to Swift?
> Yes, since the inner layout of the build folder is about to depend on the platform.
>> Does this proposal fit well with the feel and direction of Swift?
>> If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?
> `swift run` has a taste of scripting language :-)
>> How much effort did you put into your review? A glance, a quick reading, or an in-depth study?
> A read of the proposal.
> Gwendal Roué
> swift-evolution mailing list
> swift-evolution at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-build-dev