So it must be something not related to the build tools being used. At least
I went though tons of variations on those.
It could be the particular version of simulator being used for running
tests on iPhone 5. Maybe the fact that I have multiple Xcode versions
contributes to that problem... I have
> On Sep 26, 2017, at 3:57 PM, Maksym Grebenets wrote:
>
> Hi Michael
>
> Thanks for following up!
>
> I've found some extra time too to give it few more tries.
> As a matter of fact, I've tried quite a few things.
> Spoiler alert - none of them worked :)
> Here's the list of things anyways:
>
> On Sep 27, 2017, at 1:24 PM, Jiho Choi wrote:
>
> Thanks for the explanation. I modified those two locations you mentioned but
> the build failed during tests. I've been browsing the source code to figure
> out other dependences but didn't succeed yet. Could you please give me some
> poin
Thanks for the explanation. I modified those two locations you mentioned
but the build failed during tests. I've been browsing the source code to
figure out other dependences but didn't succeed yet. Could you please give
me some pointers on where to look at?
Regards,
Jiho
On Tue, Sep 26, 2017
On Wed, Sep 27, 2017 at 12:23 PM, Jordan Rose wrote:
>
>
> This is *definitely* a change that would need to go through
> swift-evolution. There are a number of potential issues and possibilities
> for breaking existing code that’s relying on this shadowing behavior,
> intentionally or unintentiona
> On Sep 26, 2017, at 18:02, Robert Widmann via swift-dev
> wrote:
>
>>
>> On Sep 25, 2017, at 10:01 AM, Nevin Brackett-Rozinsky
>> mailto:nevin.brackettrozin...@gmail.com>>
>> wrote:
>>
>> func triple(_ x: Int) -> Int {
>> return 3 * x
>> }
>>
>> extension Int {
>> func triple() -
