[swift-evolution] final + lazy + fileprivate modifiers
Matthew Johnson
matthew at anandabits.com
Mon Feb 20 11:19:59 CST 2017
> On Feb 20, 2017, at 11:02 AM, David Hart <david at hartbit.com> wrote:
>
>
>> On 20 Feb 2017, at 16:43, Matthew Johnson <matthew at anandabits.com <mailto:matthew at anandabits.com>> wrote:
>>
>>
>>> On Feb 20, 2017, at 12:31 AM, David Hart via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>>>
>>>
>>>
>>>> On 20 Feb 2017, at 00:52, Tony Arnold via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>>>>
>>>>
>>>>> On 20 Feb 2017, at 06:25, Jose Cheyo Jimenez via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>>>>>
>>>>> We need more examples to make this case.
>>>>
>>>> How do we provide those examples? This thread has been actively discussed for close to a week now, so it would be good to do something concrete about it. I think Chris’ second suggestion fits my idea of a reasonable “Default” level of privacy when starting out, and fits the model of progressive disclosure as you so excellently pointed out.
>>>>
>>>> Is this something that should go through a proper Proposal? Is someone doing this already? I’d like to help/contribute if it is.
>>>
>>> Chris' second suggestion was dropped by Chris himself after we discussed the disadvantages it adds. I am already working on a proposal to revert to Swift 2's private and it should be ready soon.
>>
>> Since you’re already drafting a proposal I will not draft the one I was thinking of.
>
> My proposal will represent my point of view (only one file-based private), but I am mentioning your suggestions in the Alternatives considered section to open debate during vote and so that the core team can decide amongst multiple alternatives.
>
> By the way, do you want to send me part of your proposal so I can copy/paste some of your arguments in the Alternatives considered section?
>
> I’d be better if the proposal represented well the different community opinions :)
Agree. I’d be happy to collaborate on helping to fill out the alternative section. I’ll write something up and send it off list for you to incorporate as desired.
>
> David.
>
>>>
>>>> thanks,
>>>>
>>>>
>>>> Tony
>>>>
>>>>
>>>>
>>>> ----------
>>>> Tony Arnold
>>>> +61 411 268 532
>>>> http://thecocoabots.com/ <http://thecocoabots.com/>
>>>>
>>>> ABN: 14831833541
>>>>
>>>> _______________________________________________
>>>> swift-evolution mailing list
>>>> swift-evolution at swift.org
>>>> https://lists.swift.org/mailman/listinfo/swift-evolution
>>>
>>> _______________________________________________
>>> swift-evolution mailing list
>>> swift-evolution at swift.org <mailto:swift-evolution at swift.org>
>>> https://lists.swift.org/mailman/listinfo/swift-evolution
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20170220/4b1b6d69/attachment.html>
More information about the swift-evolution
mailing list