+1. A very useful feature to have, indeed.
~Robert Widmann
> On May 15, 2017, at 1:47 AM, David Hart via swift-evolution
> wrote:
>
> Hello evolution (and build-dev),
>
> I’d like to pitch a QOL proposal to improve the development of command-line
> Swift Packages
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.
On Mon, May 15, 2017 at 05:45
> On 15 May 2017, at 11:58, David Hart wrote:
>
>>
>> On 15 May 2017, at 10:40, Rien wrote:
>>
>>
>>> On 15 May 2017, at 10:12, David Hart wrote:
>>>
>>>
On 15 May 2017, at 10:03, Rien wrote:
> On 15 May 2017, at 10:40, Rien wrote:
>
>
>> On 15 May 2017, at 10:12, David Hart wrote:
>>
>>
>>> On 15 May 2017, at 10:03, Rien wrote:
>>>
>>> I always wondered why it did not exist already ;-)
>>>
>>> However, I am not
> On 15 May 2017, at 10:12, David Hart wrote:
>
>
>> On 15 May 2017, at 10:03, Rien wrote:
>>
>> I always wondered why it did not exist already ;-)
>>
>> However, I am not sure if I like the “auto build” aspect. For example I may
>> have started
> On 15 May 2017, at 10:03, Rien wrote:
>
> I always wondered why it did not exist already ;-)
>
> 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 always wondered why it did not exist already ;-)
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
Hello evolution (and build-dev),
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.