> On Nov 2, 2017, at 6:07 PM, Brent Royal-Gordon wrote:
>
>> On Oct 26, 2017, at 9:28 PM, Douglas Gregor via swift-dev
>> wrote:
>>
>> Unlabeled single-value initializers are probably going to cause a number of
>> false positives, because we can’t figure out which one we meant.
>
> When we
> On Oct 26, 2017, at 9:28 PM, Douglas Gregor via swift-dev
> wrote:
>
> Unlabeled single-value initializers are probably going to cause a number of
> false positives, because we can’t figure out which one we meant.
When we're dealing with unlabeled initializers, can we use tighter rules? For
> On Nov 2, 2017, at 7:47 AM, Ted Kremenek wrote:
>
>
>
>> On Oct 31, 2017, at 11:09 PM, Douglas Gregor wrote:
>>
>>
>>
>>> On Oct 31, 2017, at 11:08 PM, Ted Kremenek wrote:
>>>
>>>
>>>
On Oct 26, 2017, at 9:28 PM, Douglas Gregor via swift-dev
wrote:
Unlabeled s
> On Oct 31, 2017, at 11:09 PM, Douglas Gregor wrote:
>
>
>
>> On Oct 31, 2017, at 11:08 PM, Ted Kremenek wrote:
>>
>>
>>
>>> On Oct 26, 2017, at 9:28 PM, Douglas Gregor via swift-dev
>>> wrote:
>>>
>>> Unlabeled single-value initializers are probably going to cause a number of
>>> fa
That sounds awesome! Don't have much time right now to check the details but
these 'near misses' have been a real problem for us.
> On 26 Oct 2017, at 9:28 pm, Douglas Gregor via swift-dev
> wrote:
>
> I have a pull request up to introduce “near-miss” warnings for protocol
> conformances:
>
> On Oct 31, 2017, at 11:08 PM, Ted Kremenek wrote:
>
>
>
>> On Oct 26, 2017, at 9:28 PM, Douglas Gregor via swift-dev
>> wrote:
>>
>> Unlabeled single-value initializers are probably going to cause a number of
>> false positives, because we can’t figure out which one we meant.
>
> Hi Do
> On Oct 26, 2017, at 9:28 PM, Douglas Gregor via swift-dev
> wrote:
>
> Unlabeled single-value initializers are probably going to cause a number of
> false positives, because we can’t figure out which one we meant.
Hi Doug,
This all looks very promising. Do you have any thoughts about how
> On Oct 29, 2017, at 10:02 AM, Tino Heth <2...@gmx.de> wrote:
>
>
>> Thoughts?
> It’s a real problem, but I think there are better ways to fight it… none the
> less, it’s the best countermeasure that is implemented now, so: Is there any
> impact on performance?
No measurable impact on perfo
> Thoughts?
It’s a real problem, but I think there are better ways to fight it… none the
less, it’s the best countermeasure that is implemented now, so: Is there any
impact on performance?___
swift-dev mailing list
swift-dev@swift.org
https://lists.swi
